Closed Bug 40956 Opened 25 years ago Closed 25 years ago

urls cuttoff in urlbar

Categories

(Core :: DOM: Editor, defect, P3)

defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: doronr, Assigned: eric)

References

Details

(Keywords: platform-parity, regression)

Long urls seem cut off in 200052908 win98 mozilla builds. However, you can click inside and when you move with the cursor, you can scroll and see portions of the url..ie, it seems that that the textarea in the XUL is shorter than the drawn one..also, one can't select the url if yo double click anywhere where there is no text. Assigning to XPT, cc:ben@netscape.com, who checked in a lot UI stuff lately.
This happens in the mozilla builds for may29 am, but not in the commercial builds -- for linux and win32. However, on mac, both mozilla and comm. builds, the urlbar is completely blank in all cases: loading a new url, selecting in the urlbar, pasting into the urlbar ...
Assignee: trudelle → beppe
Component: XP Toolkit/Widgets → Editor
OS: Windows 98 → All
Hardware: PC → All
Adding keywords. Still visible in 2000-05-29 evening builds. Gerv
Keywords: nsbeta2, pp, regression
still in 200053008.
*** Bug 41000 has been marked as a duplicate of this bug. ***
I see this problem on linux and windows commercial bits for today (2000053008)
Happens in Mac debug too. It's like the inner field for the URL bar is not being resized properly. Ben, is this you?
This is a XUL problem, nothing to do with editor. The textfield has an internal box that is not flexing properly.
Assignee: beppe → evaughan
200053108 Mozilla build WIn98...this seems to be gone. Can linux/mac people confirm this, so that we can mark this fixed?
Fixed in 2000053108 Linux. Any mac user with today's build, please confirm the fix and resolve.
Yes, this'd be gone ... mac/linux/win32 2000/05/31. marking wfm (although this may have been kin's recent changes, if not a xul change).
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.