Compatibility issues with IE11
gigouni opened this issue · 3 comments
Expected Behavior
The component should work the same on Chrome, Firefox or IE11.
Actual Behavior
I cannot make it fully work on IE11.
Steps to Reproduce the Problem
- Create new Polymer 2 project
polymer init - Install dependency
bower install --save wysiwyg-e - Run the server
polymer serve - Insert demo text 'This is a test text.'
Now, the bold works, the italic and underline too but the popups are failing. I though it was due to https://github.com/miztroh/wysiwyg-e/issues/3 but you've closed it. I didn't try with Safari but it works with Firefox.
I tried using polymer serve --compile always instead but still not working.
Do you have any clue?
Specifications
- Version: 2.1
- Platform: Windows
- Subsystem: 8.1
systeminfo
Nom de l'hôte: IE11WIN8_1
Nom du système d'exploitation: Microsoft Version d'évaluation de Wi
ndows 8.1 Entreprise
Version du système: 6.3.9600 N/A version 9600
Fabricant du système d'exploitation: Microsoft Corporation
Configuration du système d'exploitation: Station de travail autonome
Type de version du système d'exploitation: Multiprocessor Free
Propriétaire enregistré: IEUser
Organisation enregistrée:
Identificateur de produit: 00260-60000-00000-AA378
Date d'installation originale: 17/10/2013, 23:27:06
Heure de démarrage du système: 19/02/2018, 13:45:41
Fabricant du système: innotek GmbH
Modèle du système: VirtualBox
Type du système: X86-based PC
Processeur(s): 1 processeur(s) installé(s).
[01] : x64 Family 6 Model 60 Steppin
More information here
When I'm saying failing, it means that the popups are showing up really fastly but they disappear quickly without being able to apply the style to the selection.
After this, some buttons cannot be used until the page is refresh.
It seems there are several bugs plaguing IE11. I'll try to work through these. Thanks.
@gigouni: Please review the 3.x release to see if you still encounter issues. There is an open issue related to the backspacing feature, so we'll track that there. I'm closing this issue for now. Please reopen if necessary.