Known issues

Known issues

In the Web-client

The following bugs are believed to be related to the Web-client.

Known issues related to release 2.1 only

framemode=window and docDisplayMode=window

Pop-up windows that are used for XML-signing does not have any text in the title bar. "about:blank" is shown.

frameMode=window and closing the Web-client window*

If the end-user closes the new client window by clicking its close icon or pressing Alt-F4, the client is not able to detect this event causing the merchant application to hang in an unknown/unwanted state. A fix is under investigation.

Long load time when using IE and docDisplayMode=window

When using IE10/11 (on Win7 and Win 8.1 respectively) in combination with docDisplayMode = window the time it takes to load a document to be signed and the text to be displayed in the Web-client is unreasonably long compared to other browsers. This is true for all document types but is most noticeable when it comes to PDF documents.

IE and frameMode=window

frameMode=window does not work on any versions of Internet Explorer. It is recommended to avoid this combination, see BankID Web-client Merchant Application Frontend Considerations.pdf in the release documentation.

Non-optimal error handling during multi-document signing

If an end-user has more than one BankID and enters incorrect data the Web-client does not handle the error situation in the best possible way. I.e. the end-user tries to use a BankID which has been blocked due to an incorrect password has been entered too many times, the operation is aborted with a resulting error message. The end-user should have been given the option to choose another BankID in this case.

Progress spinners lack alt-text

When the Web-client displays the progress of document conversions, the progress spinners lack alt-text which prevents screen reader software from  fetching information.

The Web-client does not remember information about the last used BankID when two or more BankIDs belong to the same OTP service for a user 

When using a OTP service that has more than one BankID attached to it, the Web-client does not remember which BankID that was used for the last BankID transaction. 

Helper 2.1 and IE versions <= 8*

There is a problem with some of the obfuscated Helper-scripts for 2.1 together with IE8. The Helper will fail in 3 of 4 attempts. The error does not affect the BankID Server 2.0 mode or Merchants utilizing the Feature and UA-detection script (aka pre-check-script) or Merchants already having a fallback to other BankID clients in case of IE versions of 8 or older.

Errors during display of OTP- and password steps if the end-user only has one OTP or one BankID*

This is an error in both the WebUDD and the Web-client. A placeholder text for the input boxes of OTP and password that informs about the OTP/BankID that is default is missing if the end-user only has one OTP or one BankID. The placeholder text is displayed in cases where the end-user has more than one OTP/BankID to choose from. 

Known issues related to release 2.0 only

Sign PDF and double error messages*

When signing PDF with BankID 2.0 the error messages BID-2030 and BID-2056 may be displayed on top of each other.

Known issues related to both release 2.1 and release 2.0

Large XML documents are not scrollable when using the keyboard*

When displaying PDF or TXT documents inside the BankID Web-client the user is able to scroll using arrow keys when the document area is in focus. This is not possible for XML documents. Instead of scrolling the document the whole page is scrolled.

In the Web-client runtime environment

The following bugs and deficiencies are presumed to reside outside the solution itself, thus not fixable by BankID Norge.

Known issues related to release 2.1 only 

Android

Document signing on Android devices

Devices running Android OS appear to have a performance issue when it comes to signing with 2.1. Investigations are ongoing.

Android tablets

Soft keyboard doesn’t activate Next button in the UserID dialogue. This happens on Andriod tablets when input field of type ‘tel’ (numeric keyboard).

Android and Windows Surface with redirect

Test have shown that is not possible to change the size of the redirect page on Android devices and it is hard to do the same on Windows Surface.

iOS

iOS and scrolling documents to be signed

It is not possible to check the checkbox stating that the contents of data to be signed is understood while scrolling a document during signing. This is identified as an iOS feature which can be seen here by trying to scroll and push a button at the same time: http://jsfiddle.net/C2CRN/

iOS and scrolling documents to be signed

On some iPhone versions (mostly 4 and 5) input fields may partly be covered by the soft keyboard.

iOS 8.4 and Chrome 43 - Web-client could hang during PDF signing*

Due to high memory consumption on this combination the Web-client could hang when signing (large) PDF documents. Fortunately this combination is not one commonly used with BankID

Windows Phone

Windows Phone 8.1 - signing of PDF documents

In many cases it is not possible to navigate back in order for the Client to register that the end user has opened and read the document. Testing shows that signing of PDF documents work in UC Browser WP 8.1. 

Android and Windows Surface with redirect

Test have shown that is not possible to change the size of the redirect page on Android devices and it is hard to do the same on Windows Surface.

OS X

Mac

  • When the password is shown, the input field exhibit a possibility to enter letters from other alphabets than latin. We do not know whether this is the case for all Mac OS X versions.
  • When loading steps that require user input (userid, etc) the input field receives focus automatically. The screen reader VoiceOver doesn’t always register this, and the user needs to toggle in and out of the input field in order to get the screen reader to read out loud.

Safari < 7

Several issues have been reported with Safari versions older than 7. End users may experience that the Web-client apparently loads, but crashes without an informative error message. These versions have been added to Blacklist in order to prevent attempted loading of the Client.

The Web-client does not load on OS X 10.6.x with Safari 5.x                       

The Web-client does not load, and Apple has ended support for this combination. The combination has been added to Blacklist in order to prevent attempted loading of the Client.

Safari and frameMode and docDisplayMode = window

With Safari on Mac OS X and iOS tests have shown that pop-ups must be allowed in order to see the new window.

Firefox

Firefox reports "a script or page may be busy" in signing transactions

In some cases Firefox may report “A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue”. A detailed explanation may be found on http://kb.mozillazine.org/Unresponsive_Script_Warning.

An end user may get around the issue by pressing “continue”. The problem may be avoided by ensuring sufficient processing capacity.

Firefox on Linux, text floats over its button border*

Go to Change Password page, then the text 'Show' is larger than the size of its button.

Firefox 40 on Windows 8.1 and frameMode=window*

The contents inside the window are not formatted correctly, meaning that some of the text may be cropped.

Miscellaneous

IE and framemode=redirect

Tests have shown that using Internet Explorer with frameMode = redirect does not work when IE’s Trusted sites security levels are set to High. If Trusted sites security levels are set to Low IE displays a question to the user whether she wants to accept the redirect and then the redirect takes place.

Known issues related to release 2.0 only

iOS

iOS 2, 3, 4 and 5

The Web-client does not load on these versions. iOS 2-5 have been added to Blacklist in order to prevent attempted loading of the Client.

iOS 6.x with Mobile Safari

The Web-client does not load on this combination. The combination has been added to Blacklist in order to prevent attempted loading of the Client. 

Chrome

Chrome 14 - 24

The Web-client does not load because of use of the experimental header X-WebKit-CSP rather than the Content-Security-Policy header. These versions have been added to Blacklist in order to prevent attempted loading of the Client.

Known issues related to both release 2.1 and release 2.0

Android

HTC One

On HTC One devices using Android 4.4.3 and Stock browser, the header of a UDD is not shown if first displayed in portrait mode. If the device is tilted into landscape mode, the header appears and stays if the device is tilted back into portrait.

HTC Desire C

The keyboard covers the input field and it’s not possible to scroll down, thus leaving it impossible to see the user’s input.

HTC Desire, Android 2.3.3 and Android Browser

The Web-client does not load on this combination. It’s been verified that the Client loads on HTC Desire C with Android 4.0.3.

Samsung in general

Samsung has created their own customization of Android to support new devices, e.g. tablet Note. We’ve seen minor deviations because of errors in Samung’s customization. When bugs or deviations on Samsung devices are reported, please include the Android version and device model.

Samsung Galaxy S4 MINI – signing of XML documents

When signing XML documents on this device, the header and footer are shown, but the XML document text is not displayed.

Samsung Galaxy S2, Android 4.0.4 with Android Browser

The Web-client does not load on this combination. Please upgrade to Android 4.1.2 or newer.

Samsung Galaxy Tab 3

This device changes the keyboard display for OTP input when the device is rotated, thus overriding the instructions from the Client.

Samsung Galaxy S4 (GT-I9505) with Android 4.4.2 and Android browser

The browser freezes when loading the Client. Please use an alternative browser.

Sony Xperia mini pro, Android 4.0.4 with Android Browser

The Web-client does not load on this combination. The device times out before the Client is loaded. Please use an alternative browser.

Chrome/Nexus 5 og Nexus7

It is possible to save the password to the personal dictionary when the password is shown. Necessary markup to prevent this is included, but some browsers do not take this into account.

Dolphin JetPack

Dolphin browser on Android does not work with the Web-client if Dolphin Jetpack is activated. Please deactivate Jetpack or use an alternative browser.

iOS

iOS 7.0.x

Safari freezes when attempting to load the Web-client. Please upgrade to a newer version of iOS. The combination Safari and iOS 7.0.x has been added to Blacklist in order to prevent attempted loading of the Client.

PDF is not opened in a new tab in Chrome on iPhone 5S

The same problem arises with Chrome on iPad Mini iOS 7.1

Signing of TXT documents does not work in Chrome v40 on iOS

The Web-client displays error BID-2031 when the text to be signed is displayed. Please use another browser, e.g. Safari.

iOS Safari PDF signing

When performing signing of PDF documents on iOS Safari, cases of flickers and uneven scrolling may occur. 

iOS interprets numbers in XML as phone number and makes it into a link*

By default, Safari on iOS detects any string formatted like a phone number and makes it a link that calls the number. Specifying telephone=no disables this feature. See Apple Documentation. Merchants may put this meta tag into its XSL to prevent this feature from being activated.

iOS 8.4 Safari and show/hide password*

On iOS 8.4 Safari the web page jumps about 1 cm every time the button show/hide password is clicked/tapped.

Firefox

Firefox versions older than 29

Testing has revealed that Firefox versions older than 29 have problems with loading the Web-client. These versions have been added to Blacklist in order to prevent attempted loading of the Client. 

Firefox versions 33-35

We’ve experienced problems with Firefox v33-35 in combination with merchantURLs containing the characters ‘?’ and/or ‘;’ in regards to how Firefox handles CSP. The error is reported to Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1094067, and CSP is set to report-only for these versions.

Firefox 38

Firefox has started to store the BankID passwords in the browser, also when Merchant sites intructs it not to store passwords. Investigations to identify any workarounds are ongoing.

NVDA

NVDA reports text in incorrect format

A suspected bug in NVDA causes it to report the title "Signering [dokumentnavn]" during display of documents in a separate window or in overlay mode as a text field instead of static text.

NVDA repeats information which is no longer present

It looks like NVDA is not able to flush its memory completely when it arrives at the userid step. First, the number of documents to be signed, the name of the documents and then which document has been marked as read and understood together with the accept text are read before the user comes to the userid field. 

Chrome

Menus are closed when navigating them using Tab

When navigating menus using the Tab key in Chrome, the menu is closed rather than allowing the user to navigate up or downwards.

Miscellaneous 

Error in prng.js - registerEntropyGatherers in older browsers

When expanding feature detection we’ve experienced problems with the function registerEntropyGatherers() in prng.js.

Performance during document signing

There are still performance issues when signing large PDFs on small devices. Discussions and investigations on how to improve the performance are ongoing. A possible improvement is left for a post 2.1.0 release.

In BankID Server C

None at the time of preproduction patch release Chișinău. 

In BankID Server Java

None at the time of preproduction patch release Chișinău.

In Client Proxy

None at the time of preproduction patch release Chișinău.

Changelog

Dato Endring
05.12.14 Lagt til innslag om Windows Phone 8.1 og problemer med PDF-signering
09.12.14

Lagt til innslag om "Feil feilkode sendes til brukersted (..)" 
Oppdatert innslag om Firefox v33 og 34
Oppdatert innslag om Safari < 7

10.12.14

Oppdatert innslag om Safari < 7
Lagt til innslag "Ved bruk av BankID på mobil som OTP vises ikke referanseteksten i IE 11"
Lagt til innslag "Signering av PDF-dokumenter større enn 200 kB gir høye lastetider"

12.12.14

Oppdatert innslag om Windows Phone 8.1 og problemer med PDF-signering

19.01.15

Lagt til innslag "Firefox 35 og CSP violation, BID-2031"

28.01.15

Lagt til innslag "Signering av TXT-dokumenter fungerer ikke i Chrome 40 på iOS"

05.02.15

Følgende innslag er fjernet (er p.t. rettet i preproduksjon, og vil bli rettet i produksjon 11.2):
Bokstaver kan bli kuttet i topp eller bunn i noen nettlesere
Tekst kan gå utenfor tekstfelt på mobile enheter
verifyAuth() fra klienten ved passordbytte
Tablets/mobiltelefoner fjerner ikke soft keyboard etter ferdig autentisering

Oppdatert innslag:
Klient lastes ikke på OSX 10.6.X med Safari 5.X
Firefox 35 og CSP violation, BID-2031

Lagt til innslag:
Laster dokument-dialog blir ikke vist i Firefox pga feil i script
Firefox rapporterer "a script or page may be busy" ved dokumentsignering

12.02.15

Fjernet innslag "Ved bruk av BankID på mobil som OTP vises ikke referanseteksten i IE 11", dette ble rettet i release 2.0.4

23.03.15

Lagt til innslag "Sluttbruker får ikke en brukervennlig feilmelding ved forsøk på å laste klienten med IE8"

03.06.15

Removed Norwegian version.
Updated for BankID 2.1.0 Chișinău preproduction release. New/updated issues are marked with an asterisk.

04.08.15

Updated structure of document, and categorized known issues into "related to release 2.0", "related to release 2.1" or "related to both release 2.0 and release 2.1".
New/updated issues since last update are marked with an asterisk. 

09.09.15

Updated for BankID 2.1.0 Chișinău preproduction patch release. New/updated issues are marked with an asterisk.

14.10.15

Updated for BankID 2.1.0 Chișinău production release. New/updated issues are marked with an asterisk.