Re: [w3ctag/design-reviews] hrefTranslate attribute (#301)

Also, I'd like to add that I don't think the "single browser, single use case" conclusion is really the right one to make. Let me try to summarize why inline (though it's also in the new explainer):

Humans speak many different languages, and it is not feasible for site authors to anticipate all of the ways people who don't speak their language might interact with their site. Also, almost all users don't understand browser settings very well, and are often influenced by default settings or other factors when choosing a UI language. These problems are real, worth solving, and ones that a combination of sites and User Agent smarts can address.

If a referring site has a pretty good idea of in what language the user would want to load another site after navigation -- e.g because the user regularly visits that site -- and the user trusts the referring site site, it is a good thing that the site passes this recommendation on to the User Agent. The User Agent can then do what it thinks is best for the user at that point, which could include (a) ignoring it, (b) providing a UI to the user to give them a choice of what to do, or (c) auto-translating the site via whatever technology is desired, which could include server or client-side features.

The hint is the `hrefTranslate` attribute.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/301#issuecomment-537733187