Sitepatching updates

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

G+, skydrive, twitter, Yahoo, BofA

By Ola P. Kleivenolak. Monday, June 4, 2012 3:35:59 PM

Added patches
PATCH-680, Work around bug that disregards BASE href on G+. This was a Core regression in 11.60, causing some links to resolve wrongly. Has been properly fixed in 12.

PATCH-679, skydrive: correct MouseEvent which. When ticking checkboxes on Skydrive you're supposed to get a menu on the right side to delete, move etc. One can always read quirksmode and cry over the sorry state of interoperability here and at the same time understand why mistakes can be made in JS code in this area.

PATCH-676, RegExp parsing exception confuses Dojo, breaks BMO.com interface. Core bug. Thanks to My Opera user Hypermax for all the debugging assistance.

PATCH-671, Twitter: avoid ghost @ before username. Core bug with right-to-left mark in empty element causing double rendering of text.

PATCH-669, Fix 100.5% width search box on Yahoo! Japan. 12 only. After we improved percentage rounding in Core, some elements become too wide in the Opera-specific CSS.

PATCH-668, Broken browser sniffing prevents SafePass login on Bank of America site. This patch was developed somewhat blindly based on source sent by a user, so it has not been tested very well. Any users of BofA are encouraged to test and yell at us if we broke something p

Changed patches
PATCH-665, boortz.com: override abuse of CSS content on real elements. Formatting changes.

PATCH-418, Y!Mail Fix inserting links in mail compose screen. Avoid console spam.

Removed patches
PATCH-662, nola.com: work around abuse of CSS content on real elements. Site changed.

PATCH-641, icicibank: fix browser sniffing that causes broken positioning of slideshow on frontpage. Site changed.

PATCH-567, cnet: remove box-shadow to improve scrolling performance. Removed from 12 after Core fix.

CSS generated contentVarious sniffer and script execution order patches

Comments

Charles SchlossChas4 Monday, June 4, 2012 3:42:04 PM

Target version and time stamp of the active browser.js file is Opera Desktop 11.62 core 2.10.229, June 4, 2012. Active patches: 210 .

I knew this post was coming soon smile

Galileo Monday, June 4, 2012 5:42:16 PM

up "Active patches: 198" hope the number for 12.x will go down more smile

Valynor Monday, June 4, 2012 6:30:25 PM

Thanks for the much needed G+ fix. bigsmile

One more Google bug which is quite annoying to me: On www.youtube.com (start page ONLY) the auto-completion of the search term does not work. As soon as you press enter and get results displayed, the auto-completion now works.

Hallvord R. M. Steenhallvors Wednesday, June 6, 2012 7:48:36 AM

Originally posted by Chas4:

I knew this post was coming soon


wink

Originally posted by Valynor:

On www.youtube.com (start page ONLY) the auto-completion of the search term does not work.


It worked here when I just tested it. Do you use any content blockers or extensions that might interfere here?

Kim Jong-Ilkoyamaneko Wednesday, June 6, 2012 10:25:17 AM

No matter what I do, http://www.opera.com/docs/browserjs/ always tell that "Current browser.js status: disabled.".

I have tried to 1 and 2 at opera:config#Browser%20JavaScript without luck
If I set it to 1, it stays there but browser.js status is still disabled. If I set 2, Opera set it back to 0.

Valynor Wednesday, June 6, 2012 7:10:16 PM

Originally posted by hallvors:

It worked here when I just tested it. Do you use any content blockers or extensions that might interfere here?



Yes, I use the latest Fanboy urlfilter+css filter. Didn't think about that because it works fine on all YouTube pages *except* for the start page.

Edit: False positive reported to Fanboy.

Kim Jong-Ilkoyamaneko Friday, June 8, 2012 6:28:41 AM

Originally posted by koyamaneko:

No matter what I do, http://www.opera.com/docs/browserjs/ always tell that "Current browser.js status: disabled.".I have tried to 1 and 2 at opera:config#Browser%20JavaScript without luck If I set it to 1, it stays there but browser.js status is still disabled. If I set 2, Opera set it back to 0.


Please, any ideas what to do?

I use Windows x64, usually latest snapshots of 12.00, with HW acc. What I can do to get browser.js to work?

Hallvord R. M. Steenhallvors Friday, June 8, 2012 10:50:09 AM

Originally posted by koyamaneko:

Please, any ideas what to do?


Do you see script source code if you go to http://xml.opera.com/userjs/ - or do you get a 404 or redirect?

Kim Jong-Ilkoyamaneko Saturday, June 9, 2012 7:48:56 AM

Originally posted by hallvors:

Do you see script source code if you go to http://xml.opera.com/userjs/ - or do you get a 404 or redirect?


I see source code.

TomQyngali Sunday, June 10, 2012 1:53:36 PM

Just a suggestion, please consider adding a link to this blog on the browser.js page. smile

Kim Jong-Ilkoyamaneko Monday, June 11, 2012 11:51:45 AM

So not even sitepatching guys do not have any ideas how to get browser.js work?

Ola P. Kleivenolak Monday, June 11, 2012 2:19:13 PM

Hard to tell. Do you have a browser.js file in the profile directory? That would be in the "Preferences" path listed in opera:about

If it is there, what does the version information in it say?

Kim Jong-Ilkoyamaneko Tuesday, June 12, 2012 8:49:57 AM

I have browser.js file in profile folder. I have even downloaded latest browser.js (Opera Desktop 12.00 core 2.10.289, June 11, 2012) and set it to Opera profile folder, without luck sad

Still opera:config#Browser%20JavaScript is set to 1. If I set it to 2, Opera changes it to 0.

Ola P. Kleivenolak Tuesday, June 12, 2012 8:56:25 AM

That usually indicates something is wrong with the file - any console errors that may be related?

Kim Jong-Ilkoyamaneko Tuesday, June 12, 2012 8:57:19 AM

I do not understand what I have done differently (if anything) but now 2 stay at opera:config#Browser%20JavaScript and browser.js is enabled. I have tried this dozens of times, and I really do not understand what I did differently confused

Still, thank you for trying to help me smile

Write a comment

New comments have been disabled for this post.