-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[url_launcher] fix: tab traversal on web #10020
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
base: main
Are you sure you want to change the base?
Changes from all commits
06d560d
fad6f19
11e7825
68ec601
0b2497c
dc9fec1
d8e410d
5f2cb62
a376b78
4ac086d
a9b517e
26c49e0
e1222f1
abaaa01
30d7a0d
c724783
30c0c73
7b3465a
beb1acf
8d6d054
7aa4726
cd430f5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -117,13 +117,15 @@ class WebLinkDelegateState extends State<WebLinkDelegate> { | |
} | ||
|
||
Widget _buildChild(BuildContext context) { | ||
return Semantics( | ||
link: true, | ||
identifier: _semanticsIdentifier, | ||
linkUrl: widget.link.uri, | ||
child: widget.link.builder( | ||
context, | ||
widget.link.isDisabled ? null : _followLink, | ||
return MergeSemantics( | ||
child: Semantics( | ||
link: true, | ||
identifier: _semanticsIdentifier, | ||
linkUrl: widget.link.uri, | ||
child: widget.link.builder( | ||
context, | ||
widget.link.isDisabled ? null : _followLink, | ||
), | ||
Comment on lines
+120
to
+128
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think tests run against master AND stable (@stuartmorgan-g to confirm). If this code is expected to work with master but not with stable, then you need to wait until your flutter fix makes it to stable. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Most tests (including web integration tests) are run against master and stable, yes. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
If a test that you expected to fail is passing, that doesn't sound fine; it sounds like there's a potential test issue here that should be investigated. Am I misunderstanding? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Reading the previous (reverted) PR:
That sounds like we need to wait until the engine fix lands in stable. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I would say no, but, I'm only 50% sure about my statement and that is why I am looking for @chunhtai 's feedback as he has way more knowledge on this. But yes, from my understanding, that test should fail as my engine fix now prioritize the link flag over the button one, meaning Anyway, will wait for the fix to land on stable and then, expectt the test to fail There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The test passed CI on master, pinned to |
||
), | ||
); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chunhtai I was expecting this test to fail as the engine fix landed already 🤔
I mean now that the engine prioritize link, then ideally this test don't need
isButton: true
right? Are the tests not being ran against the master branch of the flutter?