Emphasize the bounds can be dymanically adjusted by implements#53
Emphasize the bounds can be dymanically adjusted by implements#53tunetheweb merged 4 commits intow3c:mainfrom
Conversation
And remove the recommend bounds that are out of date. Bug:w3c#50
|
quote from the current quote from the current It appears to me the original consensus is that the spec doesn't specify concrete bound values but let the implementations to decide and the values can be adjusted over time. However, the documents also recommend explicit values that inevitably would become dated and causes confusing. This PR removes the explicit values and emphasizes that the implementations can adjust the bound values. It makes it clear that adjusting the bounds to values different from the old recommend values is not a violation of the spec. |
|
@guohuideng2024 as discussed can we add an explicit mention that implementors may also choose different max/min boundaries per device? Then we're good to merge! |
Now the text mentions the boundaries can differ on different device types without mentioning "geographic regions". |
tunetheweb
left a comment
There was a problem hiding this comment.
I updated the examples as well.
Good to merge now.
And remove the recommend bounds that are out of date.
Also add "Guohui Deng" to the spec editor list.
Bug:#50