Earlier quoted context omitted.
A "toast" means a few words of salutation. That's the purpose of the Toast UI element. A user requests an action, the action returns a successful response, the user receives a message consisting of a few words announcing the success. Just because you are oblivious to the concept it doesn't mean it's bad. It just means you need to learn something before blindly asserting that stuff you don't know and are not familiar…
The point is, "because android does it" is terrible reasoning for naming the thing. It's exactly the point the author here was trying to make. Google does not control the web or define HTML standards in a vacuum, nor is it the focal point of the internet.
Introducing a new HTML element – welcome
161–170 of 234 posts
Re: Introducing a new HTML element – welcome <clippy>
#162Earlier quoted context omitted.
I do not think it is impossible, Firefox alone has rewritten several of its major components at least once. I see it more as a self-fulfilling prophecy and a constant stream of FUD from naysayers whenever such a thing is merely suggested (with popular topics being that it will never be finished, it will not be secure, if mozilla needs $500m/year how mere humans will ever be able to do it, etc). I think that a lot of…
This seems like a really strange position to fight over. OP is mainly complaining about the constant flux of the spec. At the time were KHTML was being implemented there weren't new features being released every week like we have now. In every aspect of the browser. As a single developer it is impossible to implement a browser that is compatible with today's websites.
KHTML was being implemented in 1999. That was an extremely fast moving and chaotic time in the development of the web! Browsers were shipping new features left and right, the specs didn't describe at all what browsers really did, and if you fell behind people would quickly switch to other browsers.
Even by 1999 you wouldn't have been able to make a competitive browser on your own, and especially not keep up with the rate of change.
(In the early 2000s, after Microsoft "won the first browser war" and disbanded the IE group, everything slowed way down, though.)
Re: Introducing a new HTML element – welcome <clippy>
#163Re: Introducing a new HTML element – welcome <clippy>
#164Re: Introducing a new HTML element – welcome <clippy>
#165Re: Introducing a new HTML element – welcome <clippy>
#166Earlier quoted context omitted.
> Chrome is the new IE Some software houses who supply the company I work for, are refusing to work with anything but Chrome. So it really does seem like the bad old days all over again.
It is nothing remotely like the bad old days. I'm assuming you never had to support IE6.
It's nothing remotely like the bad old days. You are correct.
It is however bad new days.
Re: Introducing a new HTML element – welcome <clippy>
#167Unlike 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…
> since when does actual real-life toast smoothly rise and fall again? Perhaps the inspiration came from the Sunbeam Radiant Control toaster: https://youtu.be/1OfxlSG6q5Y Unlike modern toasters which rudely attempt to catapult your toast into orbit, the Sunbeam gracefully and almost silently presents your toast with the love and care it deserves.
Getting it to engage was super finicky. I never saw anybody get it to work on the first try. You often had to whack it down pretty hard to make it work, while other times a light touch was sufficient. You could tell when someone was using it from across the house because you heard a metallic "whang, whang, whang, whang!", at various volumes, as they tried to get it to trigger.
Going up was super slow. (In his video, he shows it at "6x" or "12x" speed so viewers don't fall asleep.) Who would ever want that? It's done toasting. Don't make me wait 10 seconds to get my toast. Lots of singed fingers from impatient people reaching in to get their food.
The sensor wasn't very good, either. There was a razor thin margin where you'd get reasonable toast, and it was almost all the way to the "light" end. At even 25% to "dark", you'd get a block of charcoal. I'd set it all the way at "light", and toast my bread twice, if needed, because that was safest.
Lack of a manual up/down lever makes everything worse. It means you need to use the special "ONE SLICE" slot when you only have one slice. It also means if you see your bread start to catch fire (yeah), there's no easy way to get it out in a hurry. You could push the lightness all the way to "light" and hold it there (I think that was the official way), but that was unreliable. Usually, we'd just unplug it.
Also, as he notes in the video, the bread guides don't move so about all you can fit in here is a small generic white slice, and the outside gets as hot as the inside so be careful not to touch it.
This is the 2013 Mac Pro of toasters: very pretty, very clever, and a thermal nightmare. If I had infinite money and space, I'd buy one to show off, and never use it.
Re: Introducing a new HTML element – welcome <clippy>
#168Earlier quoted context omitted.
I don't really agree with the "Chrome is the new IE" sentiment. They participate in the Web Standards process the same as anyone else. That their voice has different gravity in the process due to the fact that they are often the ones pushing the standards forward isn't something they should be compared to IE for. Devs old enough to recall the halcyon days of IE know it was quite different...
> Devs old enough to recall the halcyon days of IE know it was quite different... I'm old enough. It's not different. Chrome is the new IE.
"This website supports Netscape Navigator 4."
Re: Introducing a new HTML element – welcome <clippy>
#169Earlier quoted context omitted.
While writing rendering engine isn't easy to do, it's extremely easy compared to the HTML part. Even Mozilla isn't in a hurry to rewrite all that code.
HTML parsing is not that hard compared to CSS/layout/fonts (or even figuring out layout), a competitive JavaScript engine, and the myriad of APIs and site compatibility problems OP talked about. My HTML parser uses SGML which is more generic as it takes the HTML grammar (a DTD) as parameter and computes state machine tables etc. dynamically based on it, thus a bit harder, but still very much doable.
Re: Introducing a new HTML element – welcome <clippy>
#170Earlier quoted context omitted.
> Devs old enough to recall the halcyon days of IE know it was quite different... I'm old enough. It's not different. Chrome is the new IE.
I'm old enough to remember there was a simple fix. Badges of honor you might even say! "This website supports Netscape Navigator 4."
Browser incompatibility was used to lock entire enterprises into using only Internet Explorer. Badges did nothing to help.