Bug 23763 – blur/focus events not fired on focused element when WebView loses/gains focus

• Component: DOM
• Status: RESOLVED FIXED

[Adam Roben (:aroben)]

When a WebView loses focus (e.g., by the user bringing another application to the foreground), a blur event does not fire at the focused element, but should. Firefox and IE both fire blur events at the focused element in this case.

[Adam Roben (:aroben)]

Also, when the WebView later gains focus, we should fire a focus event at the focused element.

[Adam Roben (:aroben)]

Created attachment 27352 [details]
testcase

[Ojan Vafai]

*** Bug 18815 has been marked as a duplicate of this bug. ***

[Ojan Vafai]

Also, related is 16928. Fixing this bug with out fixing bug 16928 would cause switching tabs to move your cursor to the beginning of any rich-edit field that it's in.

[Ahmad Saleem]

I am getting following in Safari Technology Preview 181:

<input> blurred
main frame blurred
main frame focused
<input> focused

^ which are expected ones.

Do we have to do anything else?

I get following from Chrome Canary 120:

<input> blurred
main frame blurred
main frame focused
<input> focused

and Firefox Nightly 120.

<input> blurred
main frame blurred
main frame focused
<input> focused

___

All browsers are matching as mentioned. Do we need to do anything else?

CCing - Abrar since he is working on event handling and Ryosuke for his input.

I think we can mark this as 'RESOLVED CONFIGURATION CHANGED'.

[Ryosuke Niwa]

This appears to have been fixed by now.