V1.2 Browser deprecation warning and compatibility warnings

I am using Firefox v61.0.1

I notice the following warnings when I load GenieACS. It might be good to consider fixing these to avoid future problems in the long life of v1.2.

  • DeprecationWarning: The option ‘tags’ will be removed in a future release, use ‘customTags’ instead.

  • This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features!

Not sure what the first one means. Any ideas?

How do you get these warnings? Using Firefox 75 and I don’t see warnings.

No I do not know specifically what the tags/customTags deprecation warning means, but I see it appear in the Firefox Web Console when I popup the Admin Config editor.

In /opt/genieacs/dist/public I have changed the presenation style in trivial ways by:

  • Replaced logo.svg with a new logo of the same size
  • Replaced favicon.png with a new favicon of the same size
  • Modified app.css to change some of the #nnnnnn colours

Otherwise I am using the standard v1.2.0 distribution, no changes to source code.

I tested with the following browsers on Windows 10 Pro (unless otherwise stated), all using the same URL to the same instance of GenieACS, at the same time, logged in as the same admin user:

Firefox 61.0.1 (64-bit) on Mint Linux

  • favicon not displayed

On launching Admin | Config | Edit xxx

DeprecationWarning: The option ‘tags’ will be removed in a future release, use ‘customTags’ instead.

Firefox 75.0 (64-bit)

  • All working OK
  • No warnings or errors in web console

Chrome Version 81.0.4044.129 (Official Build) (64-bit)

  • Logo not displayed
  • From web console:

On launching login page:

DevTools failed to load SourceMap: Could not load content for chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/sourcemaps/onloadwff.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

On opening Admin | Config | Edit xxx

deprecation.js:15 DeprecationWarning: The option ‘tags’ will be removed in a future release, use ‘customTags’ instead.

Brave [Version 1.7.98 Chromium: 81.0.4044.113 (Official Build) (64-bit)]

  • Logo not displayed. “broken image link” graphic displayed instead.
    -Web console:

On opening login page:

DevTools failed to load SourceMap: Could not load content for chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/sourcemaps/onloadwff.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

On opening Admin | Config | Edit xxx

deprecation.js:15 DeprecationWarning: The option ‘tags’ will be removed in a future release, use ‘customTags’ instead.

Edge Microsoft Edge 44.18362.449.0

  • Logo not shown
  • Web console:
    On opening login page:

HTML1527: DOCTYPE expected. Consider adding a valid HTML5 doctype: “”.

On opening Overview page:

SEC7115: :visited and :link styles can only differ by color. Some styles were not applied to :visited. [172.16.90.160:3000 (1,1)]

On opening Admin | Config | Edit xxx

DeprecationWarning: The option ‘tags’ will be removed in a future release, use ‘customTags’ instead. [2.app.js (1,83690)]

Internet Exporer IE 11.778

  • Other than the favicon being displayed in the tab, the page is completely blank and empty.
  • Nothing at all is visible in the Develop Tools

This error is appeared because the WebView can’t recognize the URL Scheme,for example, the WebView will usually recognize only http and https, anything other than these. So WebView cannot parse it to right place, we should use intent to redirect the url. for example – intent://,market://,app://,mail:// etc will not be recognized by webview unless we add a handler to handle these url scheme or by disabling these schemes and only load http and https schemes.

This error has no any specific solution till now. Android user and PC user all are facing this error which needs to be sought out. There’s a long-standing bug in Chromium regarding how links without protocols are handled. It occasionally is patched, but seems to keep resurfacing. In some cases, prefixing your links with http:// (or https://) should resolve the issue for you.

Also, in some cases, try to add target=“_blank” in your URL Scheme/Code. for example:

<a href="mailto:my@email.com" target="_blank">Link Text</a>