1

Topic: Opera and the IMT

Apologies to those who have not yet recovered from the shock of seeing a positive comment about G5 from me the other day, but here is another one.

One of my (many) gripes has been that the IMT in G5 has been mostly unworkable in Opera, though it has been unpredictable.  In the past few days, it has worked apparently as intended in Opera (touch wood, swallows and summers, etc.). Thanks for that.

As the indication has always been (even as recently as the note issued on 26 Feb) that incompatibiliity with Opera was not a priority, I wonder if the change has been an unplanned, unintended consequence of some other change.  Whatever the reason, a message to the software team: please keep it working.  I will let you know if it reverts.

I use Opera for positive reasons - not just to be different - it worked fine with G4, and G5 is the *only* site where I have to abandon Opera part-way through a session to switch to Chrome for the IMT.  It is a mark of good web design that pages are compatible with all browsers (IE creates more problems of compatibility than Opera does).

M.

2

Re: Opera and the IMT

It was always too good to be true!  Normal 'service' has been resumed this evening.

So the problem for the IT team is to determine why the IMT has been working fine for the past few days in Opera, and then fails to load in Opera this evening.  It is fine in Chrome.

M.

3

Re: Opera and the IMT

While I do agree that it should work in all Web Browsers and while Opera isn't one I would usually associate with having issues, it is unfortunately not a priority to fix in this case as Opera isn't as well used as other browsers (approx 1% of traffic to the gateway at present).

While I understand it is very annoying, we simply have other priorities for development at the moment, however if you can give us more information as to be honest Opera has always worked without issue for me with the IMT, anything that would be useful javascript console errors, request / response bodies, etc... these can at least be logged so that when we do get round to it we have somewhere to start from.

Matt Debont
Application Developer
Joint Nature Conservation Committee, Monkstone House, City Road, Peterborough PE1 1JY, UK

4 (edited by Syrphus 07-04-2014 13:20:54)

Re: Opera and the IMT

There are no error messages, Matt.  The IMT will attempt to load, gets as far as about 700kb, and stops as in the attached screenshot.

It is very difficult to be more helpful, especially as yesterday it was working perfectly through the day, and then failed in the evening, and fails again today.

M.

Post's attachments

ScreenShot_IMT.jpg 56.18 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

5

Re: Opera and the IMT

Can you look at the developer tools web inspector (Ctrl+Shift+I) and open the javascript console to see if there are any errors in there after a refresh, that looks like its a javascript error more than anything else from here.

Matt Debont
Application Developer
Joint Nature Conservation Committee, Monkstone House, City Road, Peterborough PE1 1JY, UK

6

Re: Opera and the IMT

Just done this after a refresh of https://data.nbn.org.uk/imt/?mode=SPECI … 020190485, Matt.

Opera/9.80 (Windows NT 6.2; WOW64) Presto/2.12.388 Version/12.16 (Core 2.12.388)
Type "clear()" to clear the console.
Type "// help()" for more information.
Uncaught exception: Error: Load timeout for modules: main
http://requirejs.org/docs/errors.html#timeout

Error thrown at line 141, column 8 in defaultOnError(err) in https://data.nbn.org.uk/imt/vendor/requ … equire.js:
    throw err;
called from line 537, column 20 in onError(err, errback) in https://data.nbn.org.uk/imt/vendor/requ … equire.js:
    req.onError(err);
called from line 686, column 16 in checkLoaded() in https://data.nbn.org.uk/imt/vendor/requ … equire.js:
    return onError(err);
called from line 705, column 24 in <anonymous function>() in https://data.nbn.org.uk/imt/vendor/requ … equire.js:
    checkLoaded();

Error created at line 166, column 8 in makeError(id, msg, err, requireModules) in https://data.nbn.org.uk/imt/vendor/requ … equire.js:
    var e = new Error(msg + '\nhttp://requirejs.org/docs/errors.html#' + id);
called from line 684, column 16 in checkLoaded() in https://data.nbn.org.uk/imt/vendor/requ … equire.js:
    err = makeError('timeout', 'Load timeout for modules: ' + noLoads, null, noLoads);
called from line 705, column 24 in <anonymous function>() in https://data.nbn.org.uk/imt/vendor/requ … equire.js:
    checkLoaded();>>>

Nothing at my end has changed since yesterday when it was working fine.  I am on Windows 8, javascript enabled and up to date.

M.

7

Re: Opera and the IMT

In keeping with the inconsistency that is a defining feature of G5, 0730h today IMT is working fine in Opera.  However, out of curiosity I had a look at the error window after refreshing the IMT page *when it was working (!)* and found over 500 errors (a variable number between 503 and 517 in 3 successive refreshes) some of which are pasted below and all are in the attached zipped .pdf.

I don't pretend to understand the significance of all of them, but if >500 errors are generated when the IMT is working it does not engender huge confidence.  When it next fails I will send an error list again.  The lesson of history is that that opportunity will arrive before sunset.

M.

Declaration syntax error
  set9:first-child{margin-left:76.59574468085106%;*margin-left:76.48936170212764%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  ow-fluid .offset8{margin-left:70.2127659574468%;*margin-left:70.10638297872339%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  fset8:first-child{margin-left:68.08510638297872%;*margin-left:67.9787234042553%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  w-fluid .offset7{margin-left:61.70212765957446%;*margin-left:61.59574468085106%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  et7:first-child{margin-left:59.574468085106375%;*margin-left:59.46808510638297%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  fluid .offset6{margin-left:53.191489361702125%;*margin-left:53.085106382978715%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  et6:first-child{margin-left:51.063829787234035%;*margin-left:50.95744680851063%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  w-fluid .offset5{margin-left:44.68085106382979%;*margin-left:44.57446808510638%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  ffset5:first-child{margin-left:42.5531914893617%;*margin-left:42.4468085106383%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  -fluid .offset4{margin-left:36.170212765957444%;*margin-left:36.06382978723405%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  set4:first-child{margin-left:34.04255319148936%;*margin-left:33.93617021276596%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  w-fluid .offset3{margin-left:27.659574468085104%;*margin-left:27.5531914893617%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  et3:first-child{margin-left:25.53191489361702%;*margin-left:25.425531914893618%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  -fluid .offset2{margin-left:19.148936170212764%;*margin-left:19.04255319148936%}
  --------------------------------------------------------------------------------^    Linked-in stylesheet   
********************

app.css:13
        Declaration syntax error
  ft.gradient(startColorstr='#ff5bc0de', endColorstr='#ff339bb9', GradientType=0)}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  ge:-webkit-gradient(linear,0 100%,100% 0,color-stop(0.25,rgba(255,255,255,.15)),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  100%,100% 0,color-stop(0.25,rgba(255,255,255,.15)),color-stop(0.25,transparent),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  rgba(255,255,255,.15)),color-stop(0.25,transparent),color-stop(0.5,transparent),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  ,transparent),color-stop(0.5,transparent),color-stop(0.5,rgba(255,255,255,.15)),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  t),color-stop(0.5,rgba(255,255,255,.15)),color-stop(0.75,rgba(255,255,255,.15)),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  5,255,.15)),color-stop(0.75,rgba(255,255,255,.15)),color-stop(0.75,transparent),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  r-stop(0.75,rgba(255,255,255,.15)),color-stop(0.75,transparent),to(transparent))
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  -stop(0.75,rgba(255,255,255,.15)),color-stop(0.75,transparent),to(transparent));
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Invalid value for property: background-image
  -stop(0.75,rgba(255,255,255,.15)),color-stop(0.75,transparent),to(transparent));
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  gba(255,255,255,.15) 50%,rgba(255,255,255,.15) 75%,transparent 75%,transparent);
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Invalid value for property: background-image
  gba(255,255,255,.15) 50%,rgba(255,255,255,.15) 75%,transparent 75%,transparent);
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  ground-color:#faa732;background-image:-moz-linear-gradient(top,#fbb450,#f89406);
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Invalid value for property: background-image
  ground-color:#faa732;background-image:-moz-linear-gradient(top,#fbb450,#f89406);
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  b450,#f89406);background-image:-webkit-gradient(linear,0 0,0 100%,from(#fbb450),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  );background-image:-webkit-gradient(linear,0 0,0 100%,from(#fbb450),to(#f89406))
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  ;background-image:-webkit-gradient(linear,0 0,0 100%,from(#fbb450),to(#f89406));
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Invalid value for property: background-image
  ;background-image:-webkit-gradient(linear,0 0,0 100%,from(#fbb450),to(#f89406));
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  ft.gradient(startColorstr='#fffbb450', endColorstr='#fff89406', GradientType=0)}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  ge:-webkit-gradient(linear,0 100%,100% 0,color-stop(0.25,rgba(255,255,255,.15)),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  100%,100% 0,color-stop(0.25,rgba(255,255,255,.15)),color-stop(0.25,transparent),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  rgba(255,255,255,.15)),color-stop(0.25,transparent),color-stop(0.5,transparent),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  ,transparent),color-stop(0.5,transparent),color-stop(0.5,rgba(255,255,255,.15)),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  t),color-stop(0.5,rgba(255,255,255,.15)),color-stop(0.75,rgba(255,255,255,.15)),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  5,255,.15)),color-stop(0.75,rgba(255,255,255,.15)),color-stop(0.75,transparent),
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  r-stop(0.75,rgba(255,255,255,.15)),color-stop(0.75,transparent),to(transparent))
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  -stop(0.75,rgba(255,255,255,.15)),color-stop(0.75,transparent),to(transparent));
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Invalid value for property: background-image
  -stop(0.75,rgba(255,255,255,.15)),color-stop(0.75,transparent),to(transparent));
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Unrecognized function
  gba(255,255,255,.15) 50%,rgba(255,255,255,.15) 75%,transparent 75%,transparent);
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Invalid value for property: background-image
  gba(255,255,255,.15) 50%,rgba(255,255,255,.15) 75%,transparent 75%,transparent);
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        -moz-border-radius is an unknown property
  ottom:2px;border:1px solid #e5e5e5;-webkit-border-radius:4px;-moz-border-radius:
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        -moz-transition is an unknown property
  :none;position:relative;-webkit-transition:.6s ease-in-out left;-moz-transition:
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        -moz-border-radius is an unknown property
  ground:#222;border:3px solid #fff;-webkit-border-radius:23px;-moz-border-radius:
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  ;-moz-border-radius:23px;border-radius:23px;opacity:.5;filter:alpha(opacity=50)}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        Declaration syntax error
  ntrol:focus{color:#fff;text-decoration:none;opacity:.9;filter:alpha(opacity=90)}
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        -moz-border-radius is an unknown property
  olor:inherit;background-color:#eee;-webkit-border-radius:6px;-moz-border-radius:
  --------------------------------------------------------------------------------^    Linked-in stylesheet    app.css:13
        -moz-box-sizing is an unknown property
  box-sizing:border-box;-moz-box-sizing:border-box;-webkit-box-sizing:border-box;p
  --------------------------------------^    HTML style attribute    imt/:1
        -webkit-box-sizing is an unknown property
  box-sizing:border-box;-moz-box-sizing:border-box;-webkit-box-sizing:border-box;p
  --------------------------------------------------------------------^    HTML style attribute    imt/:1
        Invalid value for property: zoom
  rder:0;display:block;overflow:hidden;width:1px;padding:1px;display:inline;zoom:1
  --------------------------------------------------------------------------------^    HTML style attribute    imt/:1
        Invalid value for property: zoom
  1
  -^    DOM style property    imt/:1
        Unknown pseudo class
  :hidden
  -------^    HTML style attribute    HTML style attribute:1

Post's attachments

IMT errors.zip 104.52 kb, 1 downloads since 2014-04-08 

You don't have the permssions to download the attachments of this post.

8

Re: Opera and the IMT

Well, I have not had to wait even as long as mid-day, never mind sunset.

0930h we are back to the usual failure.  Errors are of similar quantity, 512-513, so I will not attach a file.

M.

9

Re: Opera and the IMT

And at 1750h we are back to seemingly perfect function. If it can work sometimes, why not all the time?

M.

10

Re: Opera and the IMT

And 0725h this morning, back to no function at all.

M.

11

Re: Opera and the IMT

The problem is we are not currently changing anything on live that would affect this, are you running any addons to Opera and have you made sure it is completely upto date? I can't see why it wouldn't work in the same way as Chrome here as they are both Webkit based rendering engines so should work in roughly the same way.

Anyway we have logged the issue, but I can't see us spending a great deal of time on it right now as we simply have more important issues to resolve.

Matt Debont
Application Developer
Joint Nature Conservation Committee, Monkstone House, City Road, Peterborough PE1 1JY, UK

12

Re: Opera and the IMT

I am using the latest Opera version, Matt. No addons.  As I have indicated in these posts, the function is completely unpredictable, and after my last post of perfect function at 0725h today, it was not working at 0930h.  Now, 1029h, it is back working again.

M.