Open
Bug 302680
Opened 20 years ago
Updated 3 years ago
setting crop="none" or crop="start" in my menulist has no effect
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
UNCONFIRMED
People
(Reporter: wiggyword, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
In a Firefox extension, I have a menulist. The XUL looks roughly like:
<menulist id="XXXXXXXX"
editable="true"
class="auto-menulists"
oninput="XXXXXXXXXXXXX(event);"
onkeypress="XXXXXXXXXXXX(event);"
oncommand="XXXXXXXXXXXXXXXXXXX(event);"
onmousedown="XXXXXXXXXXXXXXXXXXXX(event, this);"
onclick="GTB_GTO_onSearchBoxClick(event, this);"
flex="1"
minwidth="50"
width="200"/>
Cropping occurs on the right side.
When i add
crop="none"
or
crop="start"
i still get cropping on the right side. the behavior i'm looking for is for no
cropping (the text just runs off the edge with no elipsis) but i tried
crop="start" just for kicks.
when i get the menulist element via javascript and display the value of the crop
property and the crop attribute of the menulist, both are "none" as i'd expect;
the rendering is just unaffected.
Reproducible: Always
Steps to Reproduce:
1. Edit XUL for a menulist and add crop="none" as an attribute
2. Install the extension
3.
Actual Results:
Text in the menulist that was too long was still cropped with an elipsis on the
right side.
Expected Results:
No cropping; text in the menulist that was too long should just stop at the
right edge with no elipsis.
Comment 1•20 years ago
|
||
The crop attribute on the menulist only applies to the display of the menulist
itself, and it seems only when the lsit is not editable. I suspect this is invalid.
Component: Toolbars → XP Toolkit/Widgets
Product: Firefox → Core
Version: unspecified → Trunk
Comment 2•20 years ago
|
||
Re-assigning to component owner.
Assignee: nobody → jag
QA Contact: toolbars → jrgmorrison
Updated•17 years ago
|
Assignee: jag → nobody
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•