Sitepatching updates

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

Marlin sync

Marlin got a major Core version bump last week, up to Presto/2.12.363. This obsoletes a number of patches. (we're only releasing a 12.50 file today)

Added patches

PATCH-774, Fix postage label printing failure with eBay/PayPal: avoid browser sniffing
PATCH-774, Fix postage label printing failure with eBay/PayPal: frame.print() bug workaround

PATCH-743, webs.com - fix reference to stylesheet variable.

Removed patches
PATCH-714, facebook: prevent chat window overflow. Core fix.

PATCH-695, area-11.com: prevent high CPU usage. Core fix.
PATCH-694, b9dm.com: prevent high CPU usage. Core fix.

PATCH-652, Fix displaying recommended items in Amazon. Core fix.

PATCH-636, uol.com.br: work around abs.pos.bottom.align core bug. Core fix.

PATCH-631, Walmart menus messed up by hasOwnProperty() regression. Core fix.

PATCH-610, GMaps: avoid autoclose of problem reporting dialog. Core fix.

PATCH-605, remove document.charset. Core fix.

PATCH-604, Facebook: work around iframe load event issue. Core fix.

PATCH-566, GMail: override overflow and fixed position styles to improve scrolling performance. Core fix.

PATCH-545, Bing Image Search adds history entries when scrolling results. Core fix.

PATCH-522, wangpiao.com: allow seat selection. Core fix.

PATCH-512, Yammer: work around missing exception when strictly comparing doc from other origin with undefined. Core fix.
PATCH-512, Yammer: work around limitation on setting document.referrer inside https IFRAME. Core fix.

PATCH-510, Yahoo!: Enable logging in with other auth services, work around cross-domain navigation block. Core fix.

PATCH-76, Make sure getAttribute() does not confuse an old BackBase lib's code where it uses namespace-like syntax. Core fix.

Hotlook?!Skydrive upload improvement, ebay shipping labels printing

Comments

Galileo Monday, August 6, 2012 5:19:24 PM

up

blackcoder Monday, August 6, 2012 8:39:08 PM

party

Michael A. Puls IIburnout426 Tuesday, August 7, 2012 5:44:41 AM

up

D1sasterp1ece Tuesday, August 7, 2012 11:34:53 AM

One question: after setting Browser Javascript (in opera:config) to '1' and checking for updates, shouldn't it automatically revert to '2'?

Ola P. Kleivenolak Tuesday, August 7, 2012 1:48:49 PM

If the update is successful yes. Note that you should not need to set it to 1, a simple "Check for updates" is enough.

D1sasterp1ece Tuesday, August 7, 2012 10:30:54 PM

So with it set to '2' checking for updates for the browser should also check for browser.js as well, but '1' forces a re-download of browser.js even if its version corresponds to what the server says, right? I assume so from '1' being explained as '1 = browser.js signature invalid'. So if a new copy of browser.js isn't downloaded, the setting won't be set to two?

Ola P. Kleivenolak Wednesday, August 8, 2012 5:24:04 PM

Yes.

metude Sunday, August 12, 2012 6:04:29 PM

http://www.shaw.ca/ - browser sniffing.

Charles SchlossChas4 Monday, August 13, 2012 5:09:47 AM

http://www.shaw.ca/ - browser sniffing.

Post in the open the web forum smile

I sent a test email w/ an attachment will see if it worked later

Write a comment

New comments have been disabled for this post.