3 ms·

Is that a proprietary HTML extension? Are we back to the IE-era mess then? If so, let's bring <marquee> back.

• Frederation 2y ago
  Man, that brought back memories.
• finnthehuman 2y ago
  >Is that a proprietary HTML extension? No, of course not. Web standards are whatever google decides they are.
• shermantanktop 2y ago
  Have you been following how HTML has evolved over the past 20 years? Your comment suggests not. It’s not entirely a standards-driven process. It’s common for browser vendors to just build stuff. That’s been a mixed blessing but it has definitely been faster than some W3C consortium debating “ergonomics” for years. Successful additions get backported into the spec, slowly.
  • deleted 2y ago
    [deleted]
• jdiff 2y ago
  Doesn't appear to be. https://github.com/whatwg/html/pull/9841 https://github.com/whatwg/html/pull/9841 https://github.com/whatwg/html/issues/9625 https://github.com/whatwg/html/issues/9625 Seems to have been in the works since 2023, out in the open, with support from all major browser engines.
• anamexis 2y ago
  TFA links to the spec - https://html.spec.whatwg.org/multipage/form-elements.html#attr-button-command https://html.spec.whatwg.org/multipage/form-elements.html#at... It's in Firefox and Safari
• deleted 2y ago
  [deleted]
• hennell 2y ago
  Marquee still works, we just don't tell marketing. https://caniuse.com/mdn-html_elements_marquee https://caniuse.com/mdn-html_elements_marquee
• slt2021 2y ago
  Chrome is the new IE. Whatever google decides will become a standard (both defacto due to them controlling the market and just shipping new version just in time and de-jure due to them financing W3C consortium and other standard bodies)