Save as MHTML adding suspect content to the file.
-
sgunhouse Moderator Volunteer last edited by
MHTML is similar to email, as you are viewing the actual saved file it is encoded like email would be (known as "quoted printable") Characters that are not safe in email are converted to an equals sign followed by a hex code - and since the = is reserved for this use, any original = must be converted to =3D (3D being the hex code for =].
The developers replied to us that removing the code would change the appearance of the page (if the page was supposed to contain any of the content blocked by Opera), and their idea was that it should look the same as it was displayed. If you don't want Opera to add that code you can (temporarily) disable the ad-blocker. They haven't clearly said they wouldn't change it - I mean, my argument to them would be that Opera will do all that when I view the saved file anyway - but of course if you (or someone you send it to) view the file in another browser you'd have all the ads back.
-
burnout426 Volunteer last edited by
@disappointeduser said in Save as MHTML adding suspect content to the file.:
the Opera browser is saving the added STYLE tags in this way..:
The markup is encoded as Quoted-Printable. That's all you're seeing there. mhtml files are basically just eml files where the main page is an attachment in the source.
-
A Former User last edited by A Former User
Dear @sgunhouse,
I understand the URL encoding and that =3D stuff.....what attract my attention is that "<=" after the "</style>" tag.
I understand what they said about the appearance of the page but what I expect is to save what I see in the browser.
If the adblocker is activated, in some way, what it is showing to me is not the original page as the ads has been removed, so why is so important to respect the original spaces coming from the ads if the page is saved to file while the browser is removing those same spaces when the page is originally displayed in the browser?
Did you get my point of view? If the argument is valid for saving it shoud be also valid for browsing. -
-
A Former User last edited by A Former User
@leocg .....
Ahhhh, got it.....
I didn't understand you correctly the first time...
But it depends if this is considered a bug or a feature as @sgunhouse, suggested.
Thanks.
-
-
burnout426 Volunteer last edited by
@disappointeduser said in Save as MHTML adding suspect content to the file.:
my attention is that "<=" after the "</style>" tag.
The '<' is the starting bracket for the LINK element on the next line. The '=' and the newline after it is just breaking up things into another line to meet line-length limits.
-
A Former User last edited by
@leocg Exactly! And that appearance is altered respect to the original page with ads, so why not save the page altered as is being displayed?
When a section is removed from a page by the adblocker, its space is not reserved in the displayed page, so the page appeareance is altered. This new page layout is what it should be saved...exactly what is displayed... with the ad links directly eliminated and tha ads space eliminated or reduced as displayed.
Maybe there is something I am missing because this sound so obvious for me...sorry.
-
A Former User last edited by
@burnout426 said in Save as MHTML adding suspect content to the file.:
@disappointeduser said in Save as MHTML adding suspect content to the file.:
my attention is that "<=" after the "</style>" tag.
The '<' is the starting bracket for the LINK element on the next line. The '=' and the newline after it is just breaking up things into another line to meet line-length limits.
It is not....it looks it belongs to the </head> tag.
So the same question is still around. Is it compliant with the standard to break the head tag inserting a "=" sign plus CRLF just before "/head>". The "=" sign is supposed to replace non printable caracter followed by its hex code, so if any it should be something like:<=OD=OA
/head>Am I wrong?
-
-
burnout426 Volunteer last edited by
@disappointeduser said in Save as MHTML adding suspect content to the file.:
It is not....it looks it belongs to the </head> tag.
Which part of the source that you previously posted are you referring to then?
As sgunhouse said though, '=' at the end of a line (as in, '=' + raw CR + raw LF) is okay. It's like a soft wrap that can happen right in the middle of an open tag or end tag etc. When the quoted-printable is decoded, it'll be put back together.
