New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 891766 link

Starred by 1 user
Status: Assigned
Owner:
█ riemerd@google.com
Last visit 27 days ago
Cc:
█ krajshree@chromium.org
█ dsexton@chromium.org
phanindra.mandapaka@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Code editor can trap focus

Project Member Reported by riemerd@google.com, Oct 3 
Platform: Windows
Chrome version: 69.0.3497.100 (Official Build) (64-bit) (cohort: Stable)
Revision:
8920e690dd011895672947112477d10d5c8afb09-refs/branch-heads/3497@{#948}
Screen reader: NVDA

(1)  Try debugging a large web app.
(2) at some point, try jumping out of that edit field by pressing b in browse mode to jump to the pretty print, or go into browse mode and press up arrow to get to the tabs list..

What is the expected result?
NVDA stays focused on the tabs.

What happens instead?
Sometimes, the edit field steels focus again. I can't figure out a reliable way to do this besides run a debugger in drive in certain weird cases. I used this HTML thinking it might produce it, but the bug is not reproduceable with it. 

```html
<html>
  <head>
    <title>Test case focus jumper bug</title>
    <script>
      var count=0;
      function a(){
        ++count;
        if(count<100)
          b()
      }
      function b(){
        ++count;
        if(count==50)
          debugger;
        if(count <100)
          a();
      }
      a();
    </script>
  </head>
</html>
```

Comment 1 by einbinder@chromium.org, Oct 4 

I have a guess as to what could be happening. When the app pauses on a debugger statement, we move to the code editor, and request the script. When we finish downloading the script, we render it and move your focus to the line that is paused. If the script is very large, there might be about a second inbetween the first focus move because the app paused, and the second focus move because the script rendered in DevTools.

Does that line up with what you are experiencing?

Comment 2 by swarnasree.mukkala@chromium.org, Oct 4

Labels: Needs-Triage-M69

Comment 3 by riemerd@google.com, Oct 4 

I'm not sure. It happens even sometimes 10 or so seconds after I've loaded the debugger. I might go into browse mode, and up arrow to the tab, and focus will jump back.

Comment 4 by leberly@chromium.org, Oct 5

Components: UI>Accessibility
Labels: -Pri-3 OS-Windows Pri-2
Adding to the a11y team's queue since NVDA is being used.

Comment 5 by leberly@chromium.org, Oct 5

Cc: dsexton@chromium.org
dsexton@, can you take a look at this?

Comment 6 by krajshree@chromium.org, Oct 16

Cc: krajshree@chromium.org
Labels: Needs-Feedback Triaged-ET
riemerd@ - Thanks for filing the issue...!!

Could you please provide a sample test file/url to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!

Comment 7 by leberly@chromium.org, Oct 19 

I see that einbinder@ has commented on this and he's the dev working in this area. Without a response from riemerd@ we will need to close this bug as archived due to inactivity. Thanks!

Comment 8 by riemerd@google.com, Oct 19 

I cannot provide a test case as of now, because I haven't figured out how
to cause it to occur outside of compiling and running drive web. if I find
anymore insite into this bug, I will post one.
Project Member

Comment 9 by sheriffbot@chromium.org, Oct 19

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by phanindra.mandapaka@chromium.org, Nov 15

Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback
@Reporter: As per comment #8, Requesting you to provided an update to it. Adding Needs-Feedback label to it.

Thanks..!

Comment 11 by paulir...@chromium.org, Dec 5

Status: Assigned (was: Unconfirmed)

Comment 12 by leberly@chromium.org, Dec 19

Labels: -Needs-Feedback
Owner: riemerd@google.com
After discussion with riemerd@, we are going to assign this to him until he can repro and answer einbinder@'s questions. No further action items right now, removing needs-feedback label.
►

Sign in to add a comment