Let's collect here sites where REALLY incompatible with current versions of KM content does present.
_{Don't post here all the sites that claim K-Meleon as "outdated browser"!}

1. twitter.com and instagram.com: embedded video from these sites doesn't play nor in KM 75 neither in 76.
The only way to view for now is to use videoosaving web-services - for example one used for VideoSaver extension

2. https://snag.gy/ - this image sharing service can upload your images (printscreens) directly from clipboard.
Now, after redesign it doesn't act so in KM 75, but works in KM 76.



Edited 1 time(s). Last edit at 08/08/2016 12:25AM by rodocop.

IMHO, it would also make sense to specify if incopatible sites work with the Firefox(Gecko) version K-meleon's code is based on.

Quote
rodocop
2. https://snag.gy/ - this image sharing service can upload your images (printscreens) directly from clipboard.

Interaction between a remote server and the clipboard is a security and privacy issue. I'd never allow it even so it will break some sites (e.g. Facebook).
There is a single scenario I can think of where this feature makes sense - namely when to parties want to exchange sensitive documents avoiding emails.
However the respective JavaScript DOM events (like many others) should be disabled by default in browsers. Unfortunaly they aren't - for better fingerprinting and tracking. No wonder that Google is pushing for such 'features'. While Firefox still lets you disable them (wonder for how long), not so with some of those 'features' in Chrome (e.g DOM -resource timing, -user timing, ...).



Edited 1 time(s). Last edit at 08/08/2016 07:24AM by Yogi.

Snag.gy also fails in FF31. This is Gecko issue.

No, probably not Gecko. I've just opened snag.gy, done what it said and saw the success.

Having said that, it was quick and dirty as I did not open an account, so I was not logged in & etc.

But it did work, see sig for sordid details. I only have pop-ups and Flash blocked, and my default UA string is <Mozilla Gecko rv:38.0 K-Meleon 76.0 20160503>.

EDIT: update global UA to reflect 76RC.

____________________
Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall" 01372 January 22, 2007 http://freefall.purrsia.com/ff1400/fv01372.htm]



Edited 1 time(s). Last edit at 08/14/2016 05:15AM by gordon451.

Quote
Yogi
Interaction between a remote server and the clipboard is a security and privacy issue. I'd never allow it ...

Yogi, what do I need to tweak (in Config??) to disable access to the clipboard?



EDIT: Found it. I think. In about:config find dom.event.clipboardevents.enabled, and toggle it to false.

This is supposed to prevent websites from hearing your bowsers' on-event signals. I do not yet know what unpleasant side effects this will have, like wrecking your password manager for example. http://www.ghacks.net/2014/01/08/block-websites-reading-modifying-clipboard-contents-firefox/ has more info.

____________________
Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall" 01372 January 22, 2007 http://freefall.purrsia.com/ff1400/fv01372.htm]



Edited 3 time(s). Last edit at 08/14/2016 06:39AM by gordon451.

gordon451,
you are right with defined pref.

As side effect it breaks at least Facebook functionality.

*************

And did you mean I need set global UA-override to (what? KM 76? FF38?) to get things working on snag.gy?



Edited 3 time(s). Last edit at 08/14/2016 09:41AM by rodocop.

Again Mega.nz got incompatible with Gecko 31 (KM75).

The solution here is to change

https://mega.nz/

to

https://eu.static.mega.co.nz/

in any Mega-related URL

On walmart.ca, the search box works fine in KM 75, but in 76 RC searching only reloads the home page. Judging by what appears in the address bar upon entering the search string, Walmart is trying to use an entirely different search script with 76 RC (and also recent Firefox versions) than with 75. In 75, for example, the URL looks like this when searching for "computers":

http://www.walmart.ca/search/computers

The URL is longer and more complicated in both KM 76 and FF 43. It will work if I type my search directly into the address bar using the older method, but some of the info in the results is missing, including some product images and more importantly, the prices! It also won't let you check whether an item is in stock in your selected store. In KM 75, on the other hand, everything on that site works perfectly.

---
Gerry



Edited 1 time(s). Last edit at 12/09/2016 05:11PM by foliator.

found it working correctly on 76

KM 76RC2 seems to work on Walmart for me. I had js enabled and user agent mode is FF compatible.

Strange! I have nothing blocked when I visit the site, and even DOM storage is enabled. At any rate it works perfectly in KM 75, in which my user agent is set to Firefox 43 and I'm using Firefox compatibility mode (Firefox itself has trouble with the site here). I also used those settings in KM 76 RC, but I don't have 76 RC on my computer at the moment.

BTW, Walmart's search feature works fine in Chromium-based browsers, too, and brings up the same simple search URL I mentioned above for KM 75.

Since you guys have no trouble with the site, it's probably not a KM incompatibility. I thought maybe my locale had something to do with this, until I remembered that it's the Canadian Walmart site, and I'm in Canada ... duh! LOL

---
Gerry

Quote
rodocop
Again Mega.nz got incompatible with Gecko 31 (KM75).

Hi rodocop - the only problem I found with https://mega.nz is the antique and broken SSL they use. The other site, https://eu.static.mega.co.nz/, uses TLS, probably because it's based in Europe where people generally seem to be a bit smarter And it also seems to be problem-free.

I've set all my browsers except Opera to use TLS, so insecure sites show up as failures. Pun intended

Oh, and I don't think you absolutely need to set any part of the UA to get into snag.gy, I meant that I had edited the post to show my current default UA string. Having said that, a lot of sites--including this Phorum--will often hit me with a 403 error, and it's amazing what my #3 UA will accomplish:
"Browser sniffing is dead. Move on. The nature of Son Gokū is... Irrepressible!!!!"

FWIW, "Son Gokū" is the Japanese rendering of "Sun Wukong", the "Monkey King".

____________________
Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall" 01372 January 22, 2007 http://freefall.purrsia.com/ff1400/fv01372.htm]



Edited 1 time(s). Last edit at 12/11/2016 02:09PM by gordon451.

gordon451,

well, you use 76 RC and it has no problem there, but 75.1 - has.

https://www.tenforums.com/performance-maintenance/69546-power-options-choose-what-power-buttons-do-change-registry.html

Displayed correctly in Edge. In KM the 'second column' is displayed extremely wide, the postings in the 'third column' are 'outside'.



Edited 1 time(s). Last edit at 12/15/2016 11:28AM by Zvonko.

Quote
Zvonko
https://www.tenforums.com/performance-maintenance/69546-power-options-choose-what-power-buttons-do-change-registry.html

Displayed correctly in Edge. In KM the 'second column' is displayed extremely wide, the postings in the 'third column' are 'outside'.

I agree. Not useable at all in KM 76RC2.

Quote
Zvonko

https://www.tenforums.com/performance-maintenance/69546-power-options-choose-what-power-buttons-do-change-registry.html

W3C Unicorn fails this page dismally in HTML (57 major errors) and CSS (24 major errors).

We note that Edge, like all IE editions, is a browser designed to: Never. Break. Webpages.

While annnoying, I cannot count this a fault in KM. The sad part is that tenforums management will simply ignore all complaints about their site not rendering properly in non-standard browsers. It is unfortunate that Pale Moon 26.2 renders the page unbroken, but then it is aimed at mainstream usage...

There are better forum sites than tenforums.

____________________
Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall" 01372 January 22, 2007 http://freefall.purrsia.com/ff1400/fv01372.htm]



Edited 1 time(s). Last edit at 12/15/2016 01:50PM by gordon451.

They made it specially to force using Edge, I think.

FF 38 fails there too. But 45 works. Chrome works with at least 20-25 last builds