Closed Bug 1425695 Opened 7 years ago Closed 5 years ago

Caret lost after move the tab to another window

Categories

(Firefox :: Tabbed Browser, defect, P3)

Product:
Firefox
Component:
Tabbed Browser
Version:
55 Branch
Platform:
All
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox57 --- wontfix
firefox58 --- wontfix
firefox59 --- wontfix
firefox60 --- fix-optional
firefox61 --- fix-optional
firefox72 --- unaffected
firefox73 --- unaffected
firefox74 --- unaffected

People

(Reporter: victor.chanfrault, Unassigned)

References

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171206182557 Steps to reproduce: - Have at least two separated Mozilla windows opened. - One of them should have a text box (if you want to see the bug). - Merge this window with an other one, to create a new tab. Actual results: In the new tab created from the separated window, every text box does not displays the blinking cursor in it, giving doubts on the selected text box. Expected results: The text boxes from the merged window should contains the blinking cursor.
Status: UNCONFIRMED → NEW
Has STR: --- → yes
status-firefox57: --- → wontfix
status-firefox58: --- → affected
status-firefox59: --- → affected
status-firefox-esr52: --- → unaffected
Component: Untriaged → Editor
Ever confirmed: true
Keywords: regression
OS: Unspecified → Windows 10
Product: Firefox → Core
Hardware: Unspecified → All
Summary: Blinking cursor missing after merging windows → Caret lost after move the tab to another window
Regression range: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6d4744a6c81c498cc81cad11b4ead64660a3d269&tochange=aa48bb3f494410de514041e8c06ca15c38680181
Blocks: 1362866
Has Regression Range: --- → yes
status-firefox58: affected → fix-optional
Component: Editor → Tabbed Browser
Product: Core → Firefox
Version: 57 Branch → 55 Branch
Mike, it sounds like this and bug 1404713 are regressions from bug 1362866. Any ideas? Could this have been fixed since then?
Flags: needinfo?(mconley)
(In reply to Julien Cristau [:jcristau] from comment #2) > Mike, it sounds like this and bug 1404713 are regressions from bug 1362866. > Any ideas? Could this have been fixed since then? Hard to say, since I can't seem to reproduce the issue locally. Perhaps I'm misunderstand the STR... is the symptom that carets _never_ appear after the tab is moved into the new window, or that the focus is removed from the text input after the merge?
Flags: needinfo?(mconley) → needinfo?(victor.chanfrault)
(In reply to Mike Conley (:mconley) (:⚙️) (Totally backlogged on reviews and needinfos) from comment #3) > (In reply to Julien Cristau [:jcristau] from comment #2) > > Mike, it sounds like this and bug 1404713 are regressions from bug 1362866. > > Any ideas? Could this have been fixed since then? > > Hard to say, since I can't seem to reproduce the issue locally. Perhaps I'm > misunderstand the STR... is the symptom that carets _never_ appear after the > tab is moved into the new window, or that the focus is removed from the text > input after the merge? On a window, you must select a text input box (so that the caret appears). After merging this window with an other one, the caret disappear. We are still able to write, so the focus is not removed from the text input. Unfocus/focus the whole window seems to solve the problem, in that way the bug looks very similar to the bug 1404713 you cited.
Flags: needinfo?(victor.chanfrault)
Flags: needinfo?(mconley)
Priority: -- → P3

Apologies - declaring needinfo bankruptcy on needinfo's greater than 2 years old.

Flags: needinfo?(mconley)

Hello,
If I can be of any help, I'm still there; but I just tested again and cannot reproduce the bug anymore. As it been fixed?

Hi,

I'm not able to reproduce this issue on Windows 10 for Firefox version Nightly 74.0a1 (2020-01-23) (64-bit) - Beta 73.0b8 (64-bit) - Release 72.0.2 (64-bit). Marking those flags as unaffected.

status-firefox72: --- → unaffected
status-firefox73: --- → unaffected
status-firefox74: --- → unaffected

This bug seems to be fixed in [2018-10-08, 2018-10-09] https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=df860e79a6a3cc41712cfd86ffbd18cf84fce626&tochange=6f8701d1be0ccf42a8e22bfce6f40056a4f58a1b.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.