Polymer/old-docs-site

Polymer.PropertiesMixin fails to create property accessors in IE11 for certain important names like "disabled"

Open

#2510 opened on Apr 10, 2018

View on GitHub
 (4 comments) (0 reactions) (1 assignee)HTML (1,013 stars) (2,482 forks)batch import
2.xbugdocsgood first issueie11platform

Description

From @bashmish on April 7, 2018 10:11

Description

Polymer.PropertiesMixin fails to create property accessors in IE11 for certain important names like disabled.

Live Demo

https://github.com/bashmish/bug-ie11-polymer-properties-mixin

Steps to Reproduce

Open tests and see what is failing in IE11 comparing to other browsers.

Expected Results

disabled has corresponding accessors that allow to react to changes.

Actual Results

No accessors are created for disabled.

Browsers Affected

This is not clear to me. I think that it's not only IE11 since the logic seems to be a little bit naive for how accessors are created. But in IE11 it's a way more problematic.

  • Chrome
  • Firefox
  • Edge
  • Safari 9
  • Safari 8
  • IE 11

Versions

  • Polymer: 2.6.0
  • webcomponents: 1.2.0

Copied from original issue: Polymer/polymer#5183

Contributor guide

Tech stack
javascriptweb components
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Polymer basicsJavaScript property descriptorsIE11 debuggingWeb components polyfills
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Examine Polymer.PropertiesMixin implementation in the Polymer source. Identify where property accessors are set and why 'disabled' might be skipped in IE11. Check for browser specific polyfills or conditionals that could interfere. Also review the reproduction repository linked in the issue for test cases.