Re: [whatwg/webidl] No "Localizable" type (#1025)

I'll just add that a recurring problem with `@dir` and `@lang` is that often OS-level components don't do anything with them. An example where this situation has come up also is with Web Share :
https://github.com/w3c/web-share/issues/6


This was also a problem with Payment Request, where data is passed to an OS level component and `@dir` and `@lang` wouldn't have any effect.

@annevk, when showing a notification, do you know if any OS actually supports doing something with `@dir` and `@lang`?

Generally speaking, over the last few years we've largely moved away from adding things to specifications that are not implemented (or implementable). I can absolutely see merit in adding `@dir` and `@lang` as "the right thing to do", but I'm concerned about adding features only to find it can't be implemented because OS level APIs don't have any means of supporting them. Naturally, this would be disappointing to developers and users. 

I know... this is a bit of a chicken and egg problem, but I don't know what the right solution is? Do we add aspirational things? or stick to "must be implemented!" to be in spec? 

As the Web becomes more integrated at the OS-level, I guess we need more OS engineers (in addition to browser folks) involved in the process too.🤔 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/issues/1025#issuecomment-934150460