3 ms·
> I can't think of single argument for including <toast> that doesn't apply at least as well for <marquee> (and the same criticism should have applied to <toas
by doctorpangloss 7y ago
> I can't think of single argument for including <toast> that doesn't apply at least as well for <marquee> (and the same criticism should have applied to <toast> too).
People browse the Internet on phones, where toasts require complex and evolving presentation and marquees do not.
You're comparing apples to oranges, marquees v. toasts. A toast is more like an audio or video tag on a mobile device. <dialog> was an example another commenter gave but missed the point completely: modals and dialogs are nuts on mobile devices!
It's about browsers taking more ownership of presentation on devices people actually use.
- yyyk 7y agoAccording to the github page, we do not get to use some system support thingy where the browser takes the toast and displays it elsewhere. The webdesigner still needs to roughly indicate where it's displayed in the page (the choices range from 'top-left' to 'bottom-right'). Unless there's something I've missed, I don't see how that's too different than adroit use of 'position', 'left' etc.