Website looks awful in basilisk

[fipsy]

Hi,

when I visit the website https://www.wieistmeineip.de, it looks awful in Basilisk. In Firefox or Chrome it looks normal. Does anyone know why?

Cheers, Volker

[New Tobin Paradigm]

DevTools Output:

Code: Select all

          vis change0  
loader.js:13:5676
AST library loaded: 0.20.0  
adlib_seq.js:1:33884
anx-mediation %cSUCCESS color: green
mediation.js:1
anx-mediation: %cSUCCESS %ccreative ids 82538608 color: green color: black
mediation.js:1
anx-mediation:  INIT --  
mediation.js:1:5022
anx-mediation:  SUCCESS 548ms  
mediation.js:1:5022
mediation_billboard_aduptech_970x250_122  
www.wieistmeineip.de:6:1
mediation_mrec_aduptech_300x600_43  
www.wieistmeineip.de:191:1
anx-mediation %cSUCCESS color: green
mediation.js:1
anx-mediation: %cSUCCESS %ccreative ids 82554566 color: green color: black
mediation.js:1
anx-mediation:  INIT --  
mediation.js:1:5022
anx-mediation:  SUCCESS 1430ms  
mediation.js:1:5022
Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive.[Learn More]  
OpenX.ashx
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing  
container.html:8
The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.  
gotoview
Use of Mutation Events is deprecated. Use MutationObserver instead.  
html5API.js:1:37578
anx-mediation %cSUCCESS color: green
mediation.js:1
anx-mediation: %cSUCCESS %ccreative ids 82540070 color: green color: black
mediation.js:1
anx-mediation:  INIT --  
mediation.js:1:5022
anx-mediation:  SUCCESS 7000ms  
mediation.js:1:5022
URIError: malformed URI sequence
Stack trace:
truste.ca.initParameterMap<@https://choices.truste.com/ca?pid=comcast01&aid=comcast01&cid=%ebuy_4094539_235853970_110766890&js=st_0:27:106
truste.ca2.initialize@https://choices.truste.com/ca?pid=comcast01&aid=comcast01&cid=%ebuy_4094539_235853970_110766890&js=st_0:37:1
@https://choices.truste.com/ca?pid=comcast01&aid=comcast01&cid=%ebuy_4094539_235853970_110766890&js=st_0:43:171
  
ca:28:27
Permission denied to access property "document"

Error Console Output:

Code: Select all

Timestamp: 4/17/2019 12:05:40 AM
Warning: An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing
Source File: https://tpc.googlesyndication.com/safeframe/1-0-32/html/container.html?n=2
Line: 8
Timestamp: 4/17/2019 12:05:40 AM
Warning: An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing
Source File: https://tpc.googlesyndication.com/safeframe/1-0-32/html/container.html?n=2
Line: 8
Timestamp: 4/17/2019 12:05:41 AM
Warning: WebRTC interfaces with the “moz” prefix (mozRTCPeerConnection, mozRTCSessionDescription, mozRTCIceCandidate) have been deprecated.
Source File: https://static.adsafeprotected.com/sca.17.4.95.js
Line: 33
Timestamp: 4/17/2019 12:06:02 AM
Warning: 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!
Source File: https://www.wieistmeineip.de/
Line: 0
Timestamp: 4/17/2019 12:06:08 AM
Warning: An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing
Source File: https://tpc.googlesyndication.com/safeframe/1-0-32/html/container.html?n=2
Line: 8

[JustOff]

This site contains a syntax error in style declarations (a single quote is missed in the url for the 'truetype' format of the FontAwesome), due to which all subsequent styles are ignored:

Code: Select all

@font-face {
 font-family:'FontAwesome';
 src:url('https://static.as.anw.net/font/fontawesome-webfont.eot?v=4.3.0');
 src:url('https://static.as.anw.net/font/fontawesome-webfont.eot?') format('embedded-opentype'),
 url('https://static.as.anw.netfont/fontawesome-webfont.woff2?v=4.3.0') format('woff2'),
 url('https://static.as.anw.net/font/fontawesome-webfont.woff?v=4.3.0') format('woff'),
 url(https://static.as.anw.net/font/fontawesome-webfont.ttf?v=4.3.0') format('truetype'),
 url('https://static.as.anw.net/font/fontawesome-webfont.svg?v=4.3.0') format('svg');
 font-weight:400;font-style:normal
}

Based on this correction interval, the solution is bug #1383075, that is confirmed by the test build.

[Moonchild]

Justoff, can you please toss me your patch? Making our style parser more robust (and better aligned with CSS3 that says to just eat whatever is between parentheses in this case if invalid) is a good thing.

[JustOff]

For the test, I applied only the main patch, but there are still changes in devtools and reftests that are necessary for completeness. I can try to arrange all this as PR a little later, when I have enough free time.

[Moonchild]

I can try to arrange all this as PR a little later, when I have enough free time

That works for me too. Thanks!

[fipsy]

Thanks a lot for your helpful investigations! If the parser is made more robust on the next basilisk, I'd better not report the bug to the site operator so we can test the functionality.

[Moonchild]

No please by all means report it. It is an error on their behalf that -will- break dislay on browsers, and it's easy to test otherwise anyway with a simple test file.

[New Tobin Paradigm]

Just because this is a situation that we can mitigate on our side to make it more tollerent to this type of error in css does not negate the fact that they indeed made one.

The fact that there IS mitigation in this case in other browsers that is open to us isn't exactly a good thing. We will try to implement it but like other browsers the error will obsured and less likely to be caught by web developers and designers.

If we had more dominance in the field I would be against this kind of mitigation of stepping over css errors and style at all costs but we aren't.

About the only area we can push back on the whole "* at all costs" stratagy and agenda is in terms of Privacy and Security of which we will never budge and follow absolute best course. Lacking a security consern though it takes more justification to not follow parity.

tl;dr Do report it to them because it is still an error on their part regardless of what we do or don't do going forward on this.

[fipsy]

I see it the same way. Smoothing out mistakes made by others is never a good solution, because it usually leads to even more mistakes. I'll report the error then. But experience has shown that little usually happens, but let's wait and see...

[New Tobin Paradigm]

All we can do is try and keep trying.