Comment by its-summertime

Comment by its-summertime 3 days ago

I'd prefer:

    <output for=input>
      <!-- bring your own time-locale component -->
      <time is=time-locale datetime=2001-02-03>2001-02-03</time>
    </output>

With the component replacing the value dependent on locale. I don't think having HTML/CSS fiddling around with making fake content is a great idea, it already causes issues with trying to copy things injected by CSS's :before/:after psudoelements, let alone having a difference between the DOM's .innerText and, well, the inner text.

Not saying decisions can't be made about these things, just that, making those decisions will pretty much make a dedicated DSL out of a single element (dependent on input, desired kind of output (absolute or relative), other data sent along side (type of currency, does it need to be a "real" currency? Since instead of just calling something in mutable/overridable JS, its now part of the HTML processing, something that can't directly be touched)

SoftTalker 2 days ago

I agree in general but I think for showing a date/time in the users chosen locale I’d make an exception. Just seems a lot easier than managing that in your application.

Reply View 1 reply

spankalee 2 days ago

That is a complete separate issue from <output> though. We'd like to do that in static parts of a page that aren't changing content from user actions.
There have been a bunch of requests for Intl-driven related elements in HTML, and I expect them to be added at some point.

Reply View | 0 replies