Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove all user agent checks for MSIE or documentMode #10014

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

niloc132
Copy link
Contributor

This removes all checks of MSIE in the user agent string, and all checks of documentMode to verify which IE version is being used, as these browsers are long since unsupported.

Most of these changes are specific to tests or devmode, but there is also a change to simplify Throwable slightly (allowing it to work in node.js and other non-browser environments), and simplification of startup user agent checks.

This removes all checks of MSIE in the user agent string, and all checks
of documentMode to verify which IE version is being used, as these
browsers are long since unsupported.

Most of these changes are specific to tests or devmode, but there is
also a change to simplify Throwable slightly (allowing it to work in
node.js and other non-browser environments), and simplification of
startup user agent checks.
@niloc132 niloc132 added this to the 2.13 milestone Oct 18, 2024
@zbynek
Copy link
Contributor

zbynek commented Oct 19, 2024

Should ScrollImpl.ScrollIImplTrident and ResizeLayoutPanel.ImplTrident be also removed to get rid of all IE specific code here?

@niloc132
Copy link
Contributor Author

Should ScrollImpl.ScrollIImplTrident and ResizeLayoutPanel.ImplTrident be also removed to get rid of all IE specific code here?

My thinking here is "yes, eventually" - the goal of this commit was to pick a few specific keywords to search and remove all traces of them (actually I skipped one that I think only appears in legacy dev mode), so as to be exhaustive about those terms. There are so many different ways to refer to old browsers that all must eventually be removed, so I would slightly prefer to go at this in stages.

So, next passes might remove all "Trident" or go after ff3.5, safari 5, android browser, etc issues, in reasonably small pieces. Some, like gwt-rpc de/serialization might be better to tackle as an entire use case at once, rather than specific keywords to search.

@niloc132 niloc132 merged commit 2ec0134 into gwtproject:main Oct 29, 2024
4 checks passed
niloc132 added a commit to niloc132/gwt that referenced this pull request Oct 29, 2024
The previous PR broke three tests which still had JSNI references to
removed methods - not caught by the "compile.tests" task. This patch
finishes removing these checks in tests, so that we never skip certain
assertions based on old browsers, which no longer exist.

Follow-up gwtproject#10014
niloc132 added a commit that referenced this pull request Oct 30, 2024
The previous PR broke three tests which still had JSNI references to
removed methods - not caught by the "compile.tests" task. This patch
finishes removing these checks in tests, so that we never skip certain
assertions based on old browsers, which no longer exist.

Follow-up #10014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants