Closed
Bug 288283
Opened 20 years ago
Closed 15 years ago
Caret sticks at the front of the filter bar in about:config when caret browsing is enabled
Categories
(Firefox :: Settings UI, defect)
Firefox
Settings UI
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: djcater+bugzilla, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050329 Firefox/1.0+ Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050329 Firefox/1.0+ When caret browsing mode is on, typing some text into the filter bar in about:config doesn't move the caret to the right of the last letter. It sticks to the very left of the filter bar and looks very odd. The virtual caret (maybe that's what it's called...) is in the correct place, as pressing backspace removes the right-most letter. Reproducible: Always Steps to Reproduce: 1. Press F7 and turn on caret browsing. 2. Open a new tab and navigate to about:config 3. Place the cursor in the filter bar. 4. Type a few characters. Actual Results: Caret didn't move, stayed at the very left. Expected Results: Caret should have moved with the text, as happens in the location bar for instance. Note: Caret browsing has to be turned on *before* opening the new tab and navigating to about:config.
Comment 1•20 years ago
|
||
This also is occuring in Windows XP SP2. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050330 Firefox/1.0+
Comment 4•18 years ago
|
||
*** Bug 345432 has been marked as a duplicate of this bug. ***
Comment 5•18 years ago
|
||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
Updated•18 years ago
|
Assignee: bugs → nobody
I still see this bug with nightly Firefox 3 trunk. Enable caret browsing. Enter about:config in URL, press return, wait 1 second till "Filter:" textbox gets focused. Input something, you will see the bug. Click somewhere in the textbox, the caret will be rendered correctly.
I don't see this anymore. Anyone else? Perhaps fixed by the focus rewrite.
Comment 8•15 years ago
|
||
I'm still seeing it in 1.1.15 and 1.1.18. I didn't try the trunk builds.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Comment 9•15 years ago
|
||
I'm not sure why the was marked as WFM since I just reported that I'm still seeing this problem, so I'll reopen. Daniel, are you saying you just aren't seeing it on the trunk, or is it working for you on the latest release? Thanks.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
| Reporter | ||
Comment 10•15 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090921 Minefield/3.7a1pre (In reply to comment #9) > I'm not sure why the was marked as WFM since I just reported that I'm still > seeing this problem, so I'll reopen. Daniel, are you saying you just aren't > seeing it on the trunk, or is it working for you on the latest release? Thanks. This bug is filed against trunk, and it works for me on trunk. If it doesn't work on a branch then it is unlikely to get fixed there. I also have no idea what the version numbers in comment 8 are.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → WORKSFORME
Comment 11•15 years ago
|
||
OK. I'm running the release 1.1.18, which was build 20090825. I tried with the latest trunk (2.1a1pre, 20090321013626) and don't see this issue, though I did find an unrelated caret bug in the trunk version.
| Reporter | ||
Comment 12•15 years ago
|
||
Ah, they're SeaMonkey versions. This was filed as a Firefox bug. If it also happens to be fixed in SeaMonkey trunk, great. For the unrelated bug you have found please file a SeaMonkey bug.
Comment 13•15 years ago
|
||
I already did, though under Core/Events. Thanks.
You need to log in
before you can comment on or make changes to this bug.
Description
•