Skip to main content

Bug Tracker

Side navigation

#14716 closed bug (fixed)

Opened January 22, 2014 02:33PM UTC

Closed January 23, 2014 06:43PM UTC

Textarea isn't cloned properly in IE11

Reported by: m_gol Owned by: dmethvin
Priority: blocker Milestone: 1.11/2.1
Component: manipulation Version: 2.1.0-rc1
Keywords: Cc: dmethvin
Blocked by: Blocking:

IE11 fails the test checking for defaultValue to be cloned properly in textarea. This causes a test to fail, see:

cc @dmethvin, you said it's about splitting one support test AFAIK, do you have a fix ready?

Attachments (0)
Change History (4)

Changed January 22, 2014 02:44PM UTC by m_gol comment:1

cc: → dmethvin
component: unfiledmanipulation
milestone: None1.11/2.1
priority: undecidedblocker
status: newopen

Changed January 22, 2014 02:45PM UTC by dmethvin comment:2

owner: → dmethvin
status: openassigned

Sorry, I don't, but I looked at it a while back. Seemed like IE11 fixed the cloning of checkboxes but not the cloning of textareas. We had both assumed by support.noCloneChecked and a single fixInput() for both. If we wanted to keep a single check we could reverse it and check a textarea, or take the hit and do two separate checks. We can do this in .1

Changed January 22, 2014 05:12PM UTC by m_gol comment:3

I'm fine with reversing the check, it'll save size and will be simpler to implement.

Changed January 23, 2014 06:43PM UTC by Dave Methvin comment:4

resolution: → fixed
status: assignedclosed

Manipulation: Use textarea for missing IE defaultValue check

IE11 fixed the checkbox defaultValue issue but not textarea. Rather than

creating a new detect name I'm reusing the old one to protect anyone who

is unwisely using this externally. Re-fixing the defaultValue when it

doesn't need to be done is not a problem, so leave that code for IE11.

Fixes #14716

Closes gh-1495

Changeset: a20494228d51c57c454ff9f10a4ba8bbdda0e49c