5 ms·
The scroll wheel and navigation don't work at all on Firefox. I really hope Chrome doesn't become the new IE. Maybe the DOJ will make Google spin off their br
by echelon 6y ago
The scroll wheel and navigation don't work at all on Firefox.
I really hope Chrome doesn't become the new IE.
Maybe the DOJ will make Google spin off their browser so the web doesn't become Google's own version of AOL.
Ten more years of this crap and Firefox will be dead.
- blinding-streak 6y agoDid you notice the domain name?
- 2fast4you 6y agoIt works fantastic on mobile safari. There’s no reason for it not to work on fire fox
- gkoberger 6y agoSafari and Chrome both come from the same original engine. It's more complicated than that (there's a lot going on under the hood), however Firefox shares no code.
- Polylactic_acid 6y agoDoes that excuse it? Last time I checked firefox did support using the scroll wheel on websites.
- BbzzbB 6y agoWorks fine on my Fox.
- pmontra 6y agoI opened it in Firefox Android (my default browser) and it worked. Then I checked with Chrome and it gets an extra rotation axis.
- eitland 6y ago> I really hope Chrome doesn't become the new IE. Too late. Ironically we who fought IE6 are partially responsible for this: if we hadn't done that Chrome wouldn't had a fighting chance and we had all had to deal with whatever Microsoft prescribed insteas ;-) On a more serious note: if we allow the Chrome monoculture to continue I guess it will prevent the next big breakthrough for the web just like IE6 held back the web for years. For those who doubt: Do you really believe Google will allow their developers to waste time on the browser once they own the market alone or do you think they will finally remove ad blocking and then go to maintenance mode? It is now our turn to fight again just like we did against IE6: - relentlessly bug any organization who creates websites or libraries that doesn't work across all modern browsers - keep suggesting regulators look into the massive market position abuse that allowed Chrome to become as dominant as it is - keep poking at Mozilla to remind them fix Firefox (it is still awesome but sadly a shadow of it former self on the extension side) - keep reminding developers that this is about professionalism and also too important to leave to PMs and execs. Finally: remember, when we started the fight against IE6 it was in many ways superior, in some ways more than Chrome today.
- skybrian 6y agoFor your prediction to come true, Chrome has to stagnate, and there are several reasons to believe it won't happen the same way: - Google is well aware of Internet Explorer's history - Automatic updates mean that there won't be an IE6 problem - Google's own web developers will push for new APIs Assuming that history will repeat seems too simple?
- zaarn 6y agoChrome does not have to stagnate to become the new IE6, browser monocultures are bad, doubly so if sponsored by an adnetwork megacorporation like Google. Besides, if all other browser engines die, why would Google continue to innovate beyond their own needs? This is already the case except they still have minor outside pressure to innovate beyond that but barely.
- teekert 6y agoI'm assuming you are not a FireFox user, otherwise you often (particularly here on HN where "fancy stuff" gets showcased) run into stuff that does not work for you. I suggest you try FF for sometime, you may find that there already is a problem.
- onion2k 6y agoThe scroll wheel and navigation don't work at all on Firefox. Looking at the source it's using three.js 62. That's from 7 years ago. This explains a lot. What's happening is that back in 2013 Chrome and IE used the non-standard 'MouseWheelEvent' while Firefox used the at-the-time-non-standard-but-is-the-standard-now 'WheelEvent'. Chrome 31 switched from MouseWheelEvent to WheelEvent[+], but that came out in Nov 2013, so when this was written it required some additional code to do cross-browser mouse wheel events (jquery.mousewheel.js in this page's code). Presumably something in that jquery plugin is still trying to do browser API detection and fires the old Firefox wheelEvent rather than the new standard version. It's a shame no one from Google went back and maintained the code for this really, but we all know how Googlers feel about maintaining old code. :) [+] Around 2012/2013 there were actually three competing mousewheel events - mousewheel[1], MouseWheelEvent[2], and WheelEvent[3]. XKCD 927 applies here (https://xkcd.com/927/ https://xkcd.com/927/). [1] https://developer.mozilla.org/en-US/docs/Web/API/Element/mousewheel_event https://developer.mozilla.org/en-US/docs/Web/API/Element/mou... [2] https://developer.mozilla.org/en-US/docs/Web/API/MouseWheelEvent https://developer.mozilla.org/en-US/docs/Web/API/MouseWheelE... [3] https://developer.mozilla.org/en-US/docs/Web/API/WheelEvent https://developer.mozilla.org/en-US/docs/Web/API/WheelEvent EDIT: Looking at the source of the plugin it also checks for "DOMMouseScroll" and "MozMousePixelScroll". I'm glad we have a standard for this now. Jeez.
- mrdoob2 6y agoThanks for debugging this! I'll see if I can fix it
- jefftk 6y agoLooks like the Wayback Machine first archived this in August 2014: https://web.archive.org/web/*/http://stars.chromeexperiments.com/ https://web.archive.org/web/*/http://stars.chromeexperiments... (Disclosure: I work for Google, speaking only for myself)
- onion2k 6y agoThat just represents when it moved from http://www.chromeexperiments.com/detail/100000-stars/ http://www.chromeexperiments.com/detail/100000-stars/ with a link to http://workshop.chromeexperiments.com/stars http://workshop.chromeexperiments.com/stars to its own subdomain. You can see it at https://web.archive.org/web/20130130122749mp_/http://www.chromeexperiments.com/detail/100000-stars/ https://web.archive.org/web/20130130122749mp_/http://www.chr...
- timvdalen 6y agoOn Chrome, the scroll wheel is reversed, which leads to a very unintuitive result.
- edumucelli 6y agoIt works for me on Firefox 81 on Debian 10.