If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Setting autocomplete on a textbox changes height

RESOLVED EXPIRED

Status

SeaMonkey
Themes
--
trivial
RESOLVED EXPIRED
15 years ago
8 years ago

People

(Reporter: Michael D. Adams, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461; .NET CLR 1.0.3705)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021001

A textbox with the type set to autocomplete is rendered differently than one 
without.  Specifily it is two pixels shorter.

Reproducible: Always

Steps to Reproduce:
Load the following XUL file:

<?xml version="1.0"?> 
<?xml-stylesheet href="chrome://communicator/skin/" type="text/css"?>
<window xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">
<textbox type="autocomplete" />
<textbox />
</window>

Actual Results:  
The first text box will be two pixels shorter than the other one when the 
classic skin is active.  Also farthest left position of the cursor is about 
three pixels farther right in the first text box.


Expected Results:  
Both text boxes should be displayed exactly the same
(Reporter)

Comment 1

15 years ago
Created attachment 101315 [details]
Screen shot of a textbox with autocomplete (top) and without (bottom)

This is a screen shot of the following XUL file in the classic skin:

<?xml version="1.0"?> 
<?xml-stylesheet href="chrome://communicator/skin/" type="text/css"?>

<window xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">
<textbox type="autocomplete" /> 
<textbox /> 
</window>

Comment 2

15 years ago
Not a problem in the modern skin, -> themes
Assignee: jaggernaut → shliang
Status: UNCONFIRMED → NEW
Component: XP Toolkit/Widgets → Themes
Ever confirmed: true
QA Contact: jrgm → pmac
(Reporter)

Comment 3

15 years ago
Created attachment 101471 [details] [diff] [review]
Patch that resolves this issue but raises another one

This is a diff on the file chrome/classic/skin/classic/global/autocomplete.css.
 However it causes/reveals another bug.  When these changes have been made the
example XUL file renders correctly, but the address bar inside the mozzila
browser is now to large by two pixels.
(Reporter)

Comment 4

15 years ago
Created attachment 101473 [details]
Screen shot of the new issue that happens when the patch is added

This screen shot displays the issue that happens when the patch is applied.  I
believe this is particular to the presence of either the icon on the left or
the button on the right.  I believe the patch is still correct and has simply
made the precence of another bug apparent.
(Assignee)

Updated

9 years ago
Product: Core → SeaMonkey
Assignee: shliang → nobody
QA Contact: pmac → themes

Comment 5

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 6

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.