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

@dbaron We've highlighted the problems the web has today more concretely. Calling out examples of how it is broken, specifically delivering content that doesn't have attribution to the original origin. 

Majortiy of the changes don't land in a specification perhaps but in the implementation of the UX for the User Agent. The UA is in control of what language the page is in. There are now prompts to confirm that the user wishes to translate the target page, and when a translation occurs. Likewise the translation engine keeps the target language for outbound links off of a translated page (this was raised as an issue and we addressed it yet it doesn't really end up much in the UX of a page).

The feedback was to make the browser as opposed to a page dictating what it should be in, and this is the case now. The attribute only serves as a possible hint with more UX apparent to the user.


-- 
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-537547914

Received on Wednesday, 2 October 2019 15:30:37 UTC