Add browser support policy for Scribble-generated documentation.#240
Add browser support policy for Scribble-generated documentation.#240samth wants to merge 2 commits into
Conversation
|
|
||
| Features that are not needed for reading and understanding the | ||
| documentation, but that are intended for developers of the | ||
| documentation or other specialized audiences, such as links to |
There was a problem hiding this comment.
"such as links to implementation" - is this the motivating use case for this pull request? (Just curious)
|
I think the requirement to have a minimal support for IE6 doesn't make much sense. IE6 by default can't even view sites with https protocol. Even when TLS1.0 is manually enabled, racket-lang.org (and most websites in the world) seems to be serving a content that IE6 doesn't understand, so it will fail with "The page cannot be displayed". This means that users who are still using it can't download Racket in the first place, so there's really no point to support it. |
|
FYI: if anyone wants to test IE (including IE6), you can use VMs provided by Microsoft. Unfortunately, Microsoft took these VMs down from their website for unknown reasons, but some users archived them. Use them at your own risk.
As noted above, for IE6, we need to enable TLS1.0 to access https websites, but racket-lang.org can't be accessed regardless. |
HTML supports the placeholder attribute, so we should use it instead of implementing it ourselves. The placeholder attribute is not available prior IE10 (not including IE10). However: 1. In non-supporting browsers (e.g., IE9), the search functionality should still work correctly. 2. Non-supporting browsers don't qualify for the "full support" level detailed in racket#240 IE9 for instance is released in 2011, and Microsoft announced its end of support in 2016.
HTML supports the placeholder attribute, so we should use it instead of implementing it ourselves. The placeholder attribute is not available prior IE10 (not including IE10). However: 1. In non-supporting browsers (e.g., IE9), the search functionality should still work correctly. 2. Non-supporting browsers don't qualify for the "full support" level detailed in #240 IE9 for instance is released in 2011, and Microsoft announced its end of support in 2016.
|
FWIW, while I don't care about IE6, I do use |
Browsers released within the last 5 years (the partial support tier according to #240) support URLSearchParams, so we should use it.
Browsers released within the last 5 years (the partial support tier according to #240) support URLSearchParams, so we should use it.
Browsers released within the last 5 years (the partial support tier according to #240) support URLSearchParams, so we should use it.
Browsers released within the last 5 years (the partial support tier according to #240) support URLSearchParams, so we should use it.
Addresses review feedback on racket#240: IE 6 can no longer establish a modern TLS connection to the docs site, so it can't load the pages at all (sorawee); replace it as the minimal-support target with text-mode browsers like lynx/links and screen readers (LiberalArtist). Also generalize the stale June-2020 usage-share example.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Resyntax analyzed 0 files in this pull request and found no issues.
| - All "evergreen" browsers current within the past 12 months (this | ||
| includes Chrome, Firefox, Safari, Edge, and other regularly-updated | ||
| browsers based on similar). "Current" means if that browser was | ||
| shipped to users within the past 12 months, it is fully supported. |
There was a problem hiding this comment.
Is the intention that this should include supported Firefox ESR releases, since they get point releases (that are not feature updates) more than once per year? https://support.mozilla.org/en-US/kb/firefox-esr-release-cycle
| styling or scripting. (Very old browsers that can no longer establish | ||
| a modern TLS connection to the documentation site, such as IE 6, are | ||
| out of scope: they cannot load the pages at all.) |
There was a problem hiding this comment.
I am not against declaring IE 6 out of scope, but the TLS criterion is about accessing documentation over the network. Isn't IE 6 still able to load locally-installed documentation pages?
4 participants
The short summary: all evergreen browsers from the past year,
plus anything <5 years old with at least 1% share on docs.racket-lang.org.
Rendered