3 ms·
It looks like a poor design desicion made 20 years ago (that wheel event is synchronous and must be run before scrolling) leads to all major browsers code becom
by codedokode 10y ago
It looks like a poor design desicion made 20 years ago (that wheel event is synchronous and must be run before scrolling) leads to all major browsers code becoming unnecessary complicated. I think it would be better to discard that design and make a new event system that would be used with new pages (and don't waste developers' resources to optimize old pages).
Maintaining compatibility is good, but at some point we need to stop and make a new design.
By the way here are the things I'd like to get fixed too:
- make a distinction between same-domain and cross-domain requests (use another HTTP method for cross-domain POST request) so all sites get XSRF vulnerability fixed
- make cross-domain requests anonymous by default
- make cookies unaccessible to Javascript by default
- stop JS loading from blocking the page so we can put script tags in the header where it makes more sense
- make as much events asynchronous as possible
- fix keyboard events, key codes and mouse buttons numbers
- make it impossible to change window.opener.location and windows.parent.location
- add CSS rules to set width for a column in a table, not for cells
- add error reporting so if some resource (like a script) fails to load the user gets a message that the page is broken
- iaml 10y agoThe situation here is IMO similar to Mozilla vs XUL, except when they actually decided to drop it a ton of people decided to drop firefox. I'm talking about compatibility in general here, not js scrolling specifically.
- wcummings 10y ago>Mozilla vs XUL What is this referring to (I know what Mozilla and XUL are, didn't know there was a tiff about it)?
- iaml 10y agoXUL will be dropped soon in favour of WebExtentions, and it doesn't offer as much flexibility as XUL. This means it won't be possible to create addons like tree-style tabs for example.
- yoasif_ 10y agoIt is being worked on: https://wiki.mozilla.org/WebExtensions/sidebarAction https://wiki.mozilla.org/WebExtensions/sidebarAction
- iaml 10y agoTree-style tabs requires not only sidebar, but also access to browser interface to hide actual tabs, which AFAIK it won't get with WebExtensions.