Skip to main content

Bug Tracker

Side navigation

#9858 closed bug (invalid)

Opened July 19, 2011 04:40AM UTC

Closed August 02, 2011 07:51AM UTC

UI issue with LABEL tag in IE6

Reported by: venkateshwar Owned by: venkateshwar
Priority: undecided Milestone: None
Component: unfiled Version: 1.6
Keywords: Cc:
Blocked by: Blocking:

Hi Team,

We were using the Jquery library in one of the web applications, recently updated to the JQuery library 1.6 version.

In IE6 browser an issue started occurring after this up gradation.

A <LABEL> tag is used for rendering a control in the UI, this <LABEL> includes a span tag with in it which holds the text shown on the browser.

See the sample HTML here:

<label for="ipprov"><span class="label">user text: </span></label> the <label> tag and the CSS class name "label" coincide in the name. The CSS class contains the property "position: relative".

This was working fine with the Jquery-1.4 version. I have also tired with the Jquery-1.6.2 version, still the same issue.

I tried to change the CSS class to a different name and it worked with the JQuery-1.6 version. Also tried to use a different element other than <LABEL> it worked.

Not sure but assuming that this name co-incidence is causing the UI to be distorted. Please let me know your views.



Attachments (0)
Change History (2)

Changed July 19, 2011 05:35AM UTC by ajpiano comment:1

owner: → venkateshwar
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced jsFiddle test case to help us assess your ticket! Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, we've created this boilerplate: Open the link and click to "Fork" in the top menu.

Changed August 02, 2011 07:51AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!