Polymer/old-docs-site

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

Open

#2,510 建立於 2018年4月10日

在 GitHub 查看
 (4 留言) (0 反應) (1 負責人)HTML (1,013 star) (2,482 fork)batch import
2.xbugdocsgood first issueie11platform

描述

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

貢獻者指南

技術棧
javascriptweb components
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Polymer basicsJavaScript property descriptorsIE11 debuggingWeb components polyfills
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
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.