Sitepatching updates

tweaking the broken code until it works, one site at a time

Some small fixes.

By Ola P. Kleivenolak. Wednesday, February 6, 2013 9:28:36 AM

Added patches

PATCH-1114, essent.nl: Don't reload during unload, you'll confuse users and yourself.

PATCH-1113, Twitter: avoid gradient paint issues when dragging overlays. Presto bug.

PATCH-1111, lifehacker: re-style abs.pos boxes. Presto bug.

PATCH-1110, lymingtonharbour.co.uk - old HVmenu.

Changed patches

PATCH-1099, YouTube comments: bad opacity animation performance in Presto. Changed filename.

Edit:
PATCH-954, Facebook images hover/context menus. Add extra selector.

Removed patches

PATCH-931, viaplay.no: dismiss browser warning. Site changed.

PATCH-911, Y!finance: delay script to load comments. Site changed.

PATCH-815, github: work around misplaced arrows. Site changed.

PATCH-682, Fix document viewer on Archives départementales de l'Aisne. Site changed.

Twitter IME++Y!News ++

Comments

vux777 Wednesday, February 6, 2013 12:21:42 PM

just a side note...
yesterday I installed 12.14 and could not get that right-click image popup menu on facebook photos (just a general page rightclick menu).After this patch, everything works fine.

Ola P. Kleivenolak Wednesday, February 6, 2013 12:25:21 PM

Yes, that was a change I forgot to mention to PATCH-954. Added an extra selector.

vux777 Wednesday, February 6, 2013 3:13:11 PM

up

Charles SchlossChas4 Wednesday, February 6, 2013 3:58:07 PM

Target version and time stamp of the active browser.js file is Opera Desktop 12.10 core 2.12.388, February 6, 2013. Active patches: 313

up

Jimtoyotabedzrock Saturday, February 9, 2013 5:15:58 PM

I think the Etherpad Lite guys could use some advice.
h
They are putting hacks back into their code just for Opera along with browser sniffing.

https://github.com/ether/etherpad-lite/issues/1463

Hallvord R. M. Steenhallvors Thursday, February 28, 2013 9:05:14 AM

Originally posted by toyotabedzrock:

They are putting hacks back into their code just for Opera along with browser sniffing.



Just looking at the diffs, without much context but it seems OK to me - I think the "fix Opera by recreating the scheduler object" checkin simply makes sure to call setTimeout() in the parent window rather than the current frame. (I assume the context is that the current frame will be navigated and timeouts created there thus would be killed - I know I'm making lots of assumptions here though wink ).

The entire Firefox sniffing block could probably be removed now. Don't know why it's still there.

Jimtoyotabedzrock Monday, March 4, 2013 4:18:52 AM

Originally posted by hallvors:

Just looking at the diffs, without much context but it seems OK to me - I think the "fix Opera by recreating the scheduler object" checkin simply makes sure to call setTimeout() in the parent window rather than the current frame. (I assume the context is that the current frame will be navigated and timeouts created there thus would be killed - I know I'm making lots of assumptions here though ).

The entire Firefox sniffing block could probably be removed now. Don't know why it's still there.



Well I think it might be pointless now to fix it since they are going to webcrash, I mean webkit.

Just do us a favor and make sure they test the desktop version with a large number of tabs open.

On the several Windows computers I have tried it hardlocks or causes a reboot.

Write a comment

New comments have been disabled for this post.