mirror of
https://github.com/nextcloud/twofactor_gateway.git
synced 2026-04-25 09:05:55 +03:00
[GH-ISSUE #284] Internet Explorer does not show all options in web frontend #64
Labels
No labels
0. to triage
1. to develop
3. to review
blocked
bug
discussion
duplicate
enhancement
enhancement
gateway:signal
gateway:signal
gateway:signal
gateway:sms
gateway:telegram
hacktoberfest
help wanted
invalid
needs info
php
pull-request
question
technical debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/twofactor_gateway-nextcloud#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @itverwaltung on GitHub (Oct 8, 2019).
Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/284
Nextcloud Version 16.0.5
Two-Factor Gateway: Version 0.14.1
Internet Explorer 11 (Tested with 11.0.9600.19504) does not show the necessary options in the gui (Security) to link an user's nc account and a sms device. Only the header of the function is shown.
The Internet Explorer Console gives this:

Please let me know if more info is needed.
Kind regards
Alex
@ChristophWurst commented on GitHub (Oct 9, 2019):
Are you familiar with JS development? We need a change like
github.com/nextcloud/mail@8a1702ddbbto make it compatible, I think.@itverwaltung commented on GitHub (Oct 9, 2019):
I don't have any knowledge in JS, sorry.
Our government will prepare to switch from Internet Explorer to Firefox. The amount of sites not working in IE is growing every day...
I would not spend to much effort in supporting Internet Explorerany more. It's like riding a dead horse.
@ChristophWurst commented on GitHub (Oct 9, 2019):
Okay, no problem.
We're in the lucky situation that we don't write the code for the browser directly, but run it through a compiler. Hence it's not even that hard to make something compatible with ie11.
I'll keep this ticket open if anyone else wants to pick this up.
@itverwaltung commented on GitHub (Oct 9, 2019):
Thanks for your effort.