162866 2016-10-03 09:47:20 -0700 Broken tab button behavior with svg <use> element 2022-08-20 15:01:17 -0700 1 1 1 Unclassified WebKit SVG Safari 10 Mac OS X 10.11 RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 arseniy.forshtreter webkit-unassigned ahmad.saleem792 ap bfulgham cfleizach fredrik rniwa simon.fraser stephanie.rewis webkit-bug-importer zalan zimmermann oldest_to_newest 1235793 0 arseniy.forshtreter 2016-10-03 09:47:20 -0700 Hi everyone. After upgrading Safari to version 10.0 one of my colleagues has noticed a very strange behavior on our service: pressing a Tab button while being focused on some of <input> elements on the page leads to focus on Safari interface elements (back button or first tab, depends whether tabs pane is visible or not) instead of a next input element. Brief research has shown that <use> element causes the problem. Here is a minimal example: https://jsfiddle.net/bwb9aq3h/ To reproduce a bug you need to focus a first <input>, press Tab and make sure that back button or tabs pane gets focused after that instead of next <input> Even though we've found a workaround (a very odd one i must say, you need to insert a whitespace around <use> like here: https://jsfiddle.net/hsrdm2vv/), we sincerely hope for this to be fixed, because it breaks user experience on a lot of websites that use svg icons. Thank you! 1236025 1 webkit-bug-importer 2016-10-03 18:41:21 -0700 <rdar://problem/28602056> 1247861 2 stephanie.rewis 2016-11-03 14:26:45 -0700 Yes, agreed. This is a very big deal. While adding space might work for some, many large sites remove whitespace automatically. This is a high priority a11y and keyboard navigation bug in my opinion. 1890892 3 ahmad.saleem792 2022-08-12 09:03:37 -0700 I am not able to reproduce this in Safari 15.6 on macOS 12.5 and it seems to be fixed in Safari Technical Preview 151 better. *** Safari 15.6 *** 1) Click on first input 2) Press Tab 3) It goes to next input 4) Press Tab again - it goes *poof* *** Safari Technical Preview 151 *** 1) Click on first input 2) Press Tab 3) It goes to next input 4) Press Tab again - it goes to address bar 5) Press Tab again - it goes to first input field again. Appreciate if someone can comment and mark this bug accordingly. Original actual results from "Comment 0" was that pressing Tab was not leading to next input field on the page. NOTE - I had JSFiddle open with "show" in the end to make it fully visible. 1892705 4 ap 2022-08-20 15:01:17 -0700 Yes, this appears fixed.