31–40 of 234 posts
The Chrome devs are thinking about whether a element would be useful. They float the proposal early on, and announce that they will implement (not ship! Web developers cannot use it) it to get some real-world experience with that to inform its design.
Still plenty of time for people to get involved, make objections, allow refinement, etc. Or am I missing something?
It gets shipped in Chrome (often without a W3C spec or substantial discussion with other stakeholders), and then other browser vendors are forced to play catch up.
Unlike the author, I do not think is a good idea. Elements are supposed to express semantics, but this just suggests behaviour. Not very descriptive behaviour either - since when does actual real-life toast smoothly rise and fall again? Possibly from the ceiling or coming in from the side? Why not just call it ? Or even better, don’t add anything - it’s surely just a that needs styling and animating with existing CSS…
In Android land, a "toast" is a particular implementation of a notification.
https://developer.android.com/guide/topics/ui/notifiers/toas...
The person writing this has to repeat frequently that they're OK with the element; it's quite funny how hard they try not to upset people. But their view of the situation is completely correct; just because this one feature might be useful (heck, when Microsoft dumped XMLHttpRequest on us that was incredible too), doesn't change the fact that we're now living in a web where Google does whatever it wants, adds whateve…
I have been repeating the Chrome is the new IE meme for the last few years. I even had a boss that only cared about our code working on Chrome and would lose it when I was demoing / developing from FireFox. I only ever demoed in Chrome just to feed that illusion that I was adhering to Chrome but I honestly dont see anything special or better and I still made sure it behaved and worked the same in both. I know people…
Earlier quoted context omitted.
I have been repeating the Chrome is the new IE meme for the last few years. I even had a boss that only cared about our code working on Chrome and would lose it when I was demoing / developing from FireFox. I only ever demoed in Chrome just to feed that illusion that I was adhering to Chrome but I honestly dont see anything special or better and I still made sure it behaved and worked the same in both. I know people…
I try switching from Chrome to Firefox at least once a year, but the UI design keeps me firmly entrenched as a Chrome user.
The person writing this has to repeat frequently that they're OK with the element; it's quite funny how hard they try not to upset people. But their view of the situation is completely correct; just because this one feature might be useful (heck, when Microsoft dumped XMLHttpRequest on us that was incredible too), doesn't change the fact that we're now living in a web where Google does whatever it wants, adds whateve…
I agree that the monopoly power situation is similar but there really is a big difference between IE hell and today's situation.
There is a big difference between one browser having a cool feature that may not be available in other browsers, versus the leading browser strangling everyone in a stasis of mediocrity, which was the case when IE/Microsoft owned the web.
Note, this is a sarcastic opening to a serious proposal — that Google not dump elements into the WHATWG HTML spec without user discussion and use cases: The way Google has gone about this seems to be… 1. Ooh! I have a cool idea! 2. Other people in Google agree with me! 3. Other Google projects could benefit from this? 4. Let's stick it in Chrome! 5. Oh, guess we should tell the community what we're doing. He thinks m…
They really should have resurrected the blink tag and added a property for the number of iterations required.
Earlier quoted context omitted.
I have been repeating the Chrome is the new IE meme for the last few years. I even had a boss that only cared about our code working on Chrome and would lose it when I was demoing / developing from FireFox. I only ever demoed in Chrome just to feed that illusion that I was adhering to Chrome but I honestly dont see anything special or better and I still made sure it behaved and worked the same in both. I know people…
I try switching from Chrome to Firefox at least once a year, but the UI design keeps me firmly entrenched as a Chrome user.
The person writing this has to repeat frequently that they're OK with the element; it's quite funny how hard they try not to upset people. But their view of the situation is completely correct; just because this one feature might be useful (heck, when Microsoft dumped XMLHttpRequest on us that was incredible too), doesn't change the fact that we're now living in a web where Google does whatever it wants, adds whateve…
Or better: Use standards which match most browsers at caniuse.com
The person writing this has to repeat frequently that they're OK with the element; it's quite funny how hard they try not to upset people. But their view of the situation is completely correct; just because this one feature might be useful (heck, when Microsoft dumped XMLHttpRequest on us that was incredible too), doesn't change the fact that we're now living in a web where Google does whatever it wants, adds whateve…
There is a difference though: when Firefox was launched, it was still possible to develop a browser from scratch (like Opera was doing back then), and hence lively competition. Nowadays, with WHATWG HTML's feature creep (the HTML "living standard" spec alone weighing in at 1250 pages and 13.3 MB as a PDF, plus tens of CSS specs all over the place, and JavaScript a moving target), that's infeasible for even a nation-s…