A forum to discuss the Gargoyle web interface for Openwrt
https://www.gargoyle-router.com/phpbb/
I take back what I said, found this thanks to helpful people on #io.js : https://github.com/imyller/meta-nodejsLantis wrote:Cool. Well thanks for looking into it
Hi there Eric it's me that was talking about a screen reader mate not the op. I dont think the op was on about node.js in his op. i think he wanted to no about html5 and node.js came up as a after thought! All though i was shocked to read about that9 meg blob.lolEric wrote:Node.js is not going to work. One of the comments in that second link in the post above indicates a binary size of 9.6M. Gargoyle needs to work on routers that have an entire flash disk size of 4M , so... no. It's just too big. The primary reason things are the way they are is to maximize load speed while still keeping the amount of disk space and memory required as low as possible.
That said.. you were complaining about iframes. I realize you're looking at the code with a screen reader, so you may have missed it, but all of the iframes have the property style="display:none" which means they are never displayed to the user. They are there so I can submit a form to the iframe and the browser won't redirect off the page, not to actually display any information.
Also, I absolutely will accept pull requests if they improve accessibility and don't break existing functionality or expand the the size of the build too much (It still needs to fit on 4M routers).
Thank you for taking the time to post here, EricEric wrote:Node.js is not going to work. One of the comments in that second link in the post above indicates a binary size of 9.6M. Gargoyle needs to work on routers that have an entire flash disk size of 4M , so... no. It's just too big. The primary reason things are the way they are is to maximize load speed while still keeping the amount of disk space and memory required as low as possible.
That said.. you were complaining about iframes. I realize you're looking at the code with a screen reader, so you may have missed it, but all of the iframes have the property style="display:none" which means they are never displayed to the user. They are there so I can submit a form to the iframe and the browser won't redirect off the page, not to actually display any information.
Also, I absolutely will accept pull requests if they improve accessibility and don't break existing functionality or expand the the size of the build too much (It still needs to fit on 4M routers).
Code: Select all
<script src="./js/common.js?1.8.X--Built-20150922-0340-git-04e6ec1-"></script>Code: Select all
function setBrowserTimeCookie()
{
var browserSecondsUtc = Math.floor( ( new Date() ).getTime() / 1000 );
// if localStorage is present, use that
if (('localStorage' in window) && window.localStorage !== null) {
// easy object property API
localStorage.browser_time = browserSecondsUtc;
//sessionStorage is also available
} else {
document.cookie="browser_time=" +browserSecondsUtc + "; path=/"; //don't bother with expiration -- who cares when the cookie was set? It just contains the current time, which the browser already knows
}