Bug 1678103 Comment 11 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I remembered an odd bug I reported in bug 1847566. (Not sure if it is related in anyway, but it has a parallel feel to this one and might be a place to investigate.)
Revision 1 by
on 
I remembered an odd bug I reported in bug 1847566. (Not sure if it is related in any way, but it has a parallel feel to this one and might be a place to investigate.)
Revision 2 by
on 
I remembered an odd bug I reported in bug 1847566. 

Not sure if it is related in any way, but it has a parallel feel to this one and might be a place to investigate. It had differing behavior in GVE and Fenix. Additionally, the bug reproduced by switching tabs and touching content a certain way. For example, touching content v. not touching the content when switching tabs caused different behavior with `primary = true` and `primary = false` on the browser.
Revision 3 by
on 
I remembered an odd bug I reported in bug 1847566. 

Not sure if it is related in any way, but it has a parallel feel to this one and might be a place to investigate. That bug had differing behavior in GVE and Fenix. Additionally, the bug reproduced by switching tabs and touching content a certain way. For example, touching content v. not touching the content when switching tabs caused different behavior with `primary = true` and `primary = false` on the browser.
Revision 4 by
on 
I remembered an odd bug I reported in bug 1847566. 

Not sure if it is related in any way, but it has a parallel feel to this one and calls around `setFocused` and `setActive` might be a place to investigate. That bug had differing behavior in GVE and Fenix. Additionally, the bug reproduced by switching tabs and touching content a certain way. For example, touching content v. not touching the content when switching tabs caused different behavior with `primary = true` and `primary = false` on the browser.
Revision 5 by
on 
I remembered an odd bug I reported in bug 1847566. 

Not sure if it is related in any way, but it has a parallel feel to this one, and calls around `setFocused` and `setActive` might be a place to investigate. That bug had differing behavior in GVE and Fenix. Additionally, the bug reproduced by switching tabs and touching content a certain way. For example, touching content v. not touching the content when switching tabs caused different behavior with `primary = true` and `primary = false` on the browser.

Back to Bug 1678103 Comment 11