Unless you have very specific developer use cases, FF and Chrome dev tools are virtually identical. So assuming the browsers are largely identical for most reasonable intents, what's the rationale behind saying everyone should abandon one for another? if they're all the same then how do you make a value judgment? or are you just of the mind that everyone should use the exact same web browser for the sake of consistency, like in north korea? that all else being equal, firefox users should abandon firefox for chrome because it has a higher market share? speaking of which, firefox adheres more closely than chrome does, so if that was a criteria for being a "real" browser firefox would be winning. the implementation might differ but the standards are almost the same. even though that's actually wrong, it's true in spirit. and you said yourself in another post in this thread that they're 99% identical. if any extant browser has a claim to being a "real" web browser it's firefox.īut it's a ridiculous criterion in the first place. but why are you posting in here if you think firefox is not a "real browser"? you spend your time just shouting over the internet at fans of products you don't like? and what about firefox is not "real"? the precursor to mozilla literally invented the web browser. are you suggesting that the majority of major commercial web businesses, down to facebook, twitter, and google itself, are managed by failures?ītw, I wasn't trying to get dragged into some childish argument about whose browser is the best. anyway, if your appraisal was correct, then all manner of businesses that actually develop major commercial projects would behave just like you're suggesting, and only test for chrome. and anyone getting into it would see the MDN support table and immediately get either very intimidated, or very anal about testing, depending on their personality I guess lol I never doubted that, that's just a basic convention.Īnd your example seems a little disingenuous, I think anyone working on a commercial wasm project would be testing both firefox and chrome and potentially others, whether they're trying to do something really obscure and pointless with it or not, because no web developer on earth fully understands each browser's unique implementation lol. but for major projects, single page sites, PWAs, more cutting-edge stuff, of course you will need to test several browsers, and not just different browsers but older versions of each. of course for simple projects you can expect everything you envision to work in any modern browser. and especially with 3D I think firefox still has some significant hit detection bugs. There are differences in canvas, both 2D and 3D.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |