Skip to main content

Search and Top Navigation

#8879 closed bug (cantfix)

Opened December 03, 2012 10:50PM UTC

Closed December 04, 2012 09:59PM UTC

Last modified December 05, 2012 01:50PM UTC

Accordion: Setting maxlength on an input inside an accordion panel sometimes fails in Firefox

Reported by: debugginglife Owned by:
Priority: minor Milestone: 1.10.0
Component: ui.accordion Version: 1.9.2
Keywords: Cc:
Blocked by: Blocking:

When i use accordion feature in two panels and try to set maxlength of an input field by using a js function in other panel, the maxlength value changes in mozilla Firefox in value (i checked via firebug) however it does not change on the field (you can not edit).

It works fine for chrome but not Firefox. Is this a real bug and what is the solution?

You can see the bug in detail:

To see error: at start the maxlength sets to 4. when you open second tab and click the link it aims to set it to 45. however the maxlength value changes but you can not edit the field

Attachments (0)
Change History (6)

Changed December 04, 2012 12:48AM UTC by scottgonzalez comment:1

status: newopen
summary: input[text] maxlength seems to be set however it can not be set on Firefox.Accordion: Setting maxlength on an input inside an accordion panel sometimes fails in Firefox

Reduced test case:

Changed December 04, 2012 04:07AM UTC by tj.vantoll comment:2

Interestingly the example works as expected in Firefox 3.6 and fails in Firefox >= 4.

Changed December 04, 2012 09:59PM UTC by scottgonzalez comment:3

resolution: → cantfix
status: openclosed

This is not something we can fix:

I'll report this to Mozilla.

Changed December 04, 2012 10:12PM UTC by scottgonzalez comment:4

Changed December 05, 2012 10:50AM UTC by debugginglife comment:5

_comment0: Thanks Scott... \ \ Similar behavior is observed when trying to change selected option of a select box.1354707707335309

Thanks Scott...

when you make elem.maxLength = 10; with Capital 'L' it works, may it lead to a solution ?

Changed December 05, 2012 01:50PM UTC by scottgonzalez comment:6

Thanks for catching that. I missed something important in my reduction because the failure was masked by the incorrect capitalization of the property name. It turns out the problem only occurs if the original maxlength and style are set via JS. I've updated the test case that I submitted to Mozilla, you can see it here: