Sitepatching updates

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

Fail whale update

By Hallvord R. M. Steenhallvors. Tuesday, July 17, 2012 8:47:11 AM

Oops, we broke Twitter. A good reason to get a new browser.js update out.

New patches:

PATCH-325 Y!Mail work around browser blocking (Yahoo Mail Japan only)
PATCH-730 Menu misplaced on treasury.gov due to window.opera sniffing in .NET JS library
PATCH-738 Work around sniffing hiding submit buttons on passport2.hp.com
PATCH-741 Avoid an Opera pushState() and URL resolution bug that breaks navigation on help.adobe.com
PATCH-736 Work around browser sniffing that hides Spain's stock exchange's menu. We'll see if this has any positive effect on the Spanish economy..
PATCH-734 Avoid IE PNG transparency bug workaround that hides submit button on E-pagofacil
PATCH-742 Work around browser sniffing that breaks traffic.com
PATCH-744 Twitter: work around comma-separated statement limit in Carakan ES engine

Changed patches

PATCH-689 talenthouse.com: work around browser sniff changed to avoid browser warning screen entirely, rather than clicking through it automatically

Removed patches

PATCH-559 Browser sniffing on Raku Bus (site changed)
Betfair relies on firstChild defined on attribute nodes (older patch, noticed this week that we have had a core fix for quite a while..)

So, now we just hope you get the new browser.js before you try to use the updated Twitter. smile

New Disqus and some sniffer workarounds.Hotlook?!

Comments

Mimis Mum (MM)mimi_s_mum Tuesday, July 17, 2012 9:36:02 AM

Oops, we broke Twitter.

http://files.myopera.com/Tamil/Smilies/ROFL.gif - http://files.myopera.com/Tamil/Smilies/ROFL.gif - http://files.myopera.com/Tamil/Smilies/ROFL.gif -
Yes. We noticed. bigsmile

Thanks for the fix. yes The latest patch for 12.00 is

Target version and time stamp of the active browser.js file is Opera Desktop 12.00 core 2.10.289, July 17, 2012. Active patches: 218 .

vinyldeck Tuesday, July 17, 2012 10:16:16 AM

How do I get the latest patch for Opera 11.64?

netmain Tuesday, July 17, 2012 10:17:30 AM

thanks for the fixes

but, here, with opera 12.01 and opera 12.50, twitter loads only the first page of tweets, the timeline doesn't work. I still get the new tweets, but I can't load the old ones.

also, the links ( #something ) stopped working.

I tried with browser.js enabled and disabled .. same results.

thank you.

Edit: everything works now !! it seems to be fixed in the twitter side !!!

vinyldeck Tuesday, July 17, 2012 10:43:28 AM

Can we get a new js patch for Opera 11.64?

Swapnil RustagiSwapnil99pro Tuesday, July 17, 2012 10:52:42 AM

Opera 11.64 users:

Download browser.js from http://get.geo.opera.com/res/servicefiles/userjsfiles/all/browserjs-desktop-11.65-20120717.js (easy way; open this link using IE, it will offer you to save it, unlike Opera which will open it)

and save it to the computer. Rename it to browser (or browser.js if file extensions are shown on your system) and place it into the Opera directory

(C:\Users\USERNAME\AppData\Roaming\Opera\Opera for Windows Vista and 7; for other platforms, find 'Opera directory' under Paths in opera:about).

(Copy browser.js into Opera directory while Opera is closed, after viewing the Paths in opera:about just close Opera and copy the file).

EDIT: Thanks to http://my.opera.com/community/forums/findpost.pl?id=7008582 for location of all BrowserJS files.

And, after you download, rename and copy this file to Opera directory, http://www.opera.com/docs/browserjs/ should show: "Opera Desktop 11.62 core 2.10.229, July 17, 2012. Active patches: 231"

netwolf Tuesday, July 17, 2012 11:34:25 AM

Thank you for the instructions, but shouldn't updating the browser.js file of the latest _really_ stable release (11.64) be WAY more user friendly?

I too merely get the update dialog (which I naturally decline), but no browser.js update with 11.64 on Win 7.

Swapnil RustagiSwapnil99pro Tuesday, July 17, 2012 11:45:28 AM

Originally posted by netwolf:

_really_ stable release (11.64)


Depends, I am myself using Opera 12.00 on both XP and 7 - and I find them good in stability. (Now, please, I do not use M2, Feeds, IRC, pinned tabs, stacked tabs - so don't post a list of problems).

Originally posted by netwolf:

I too merely get the update dialog (which I naturally decline), but no browser.js update with 11.64 on Win 7.


Not even after following those instructions above?

ouzowtfouzoWTF Tuesday, July 17, 2012 11:49:28 AM

Originally posted by sitepatching:

We'll see if this has any positive effect on the Spanish economy..


bigsmile http://files.myopera.com/Tamil/Smilies/ROFL.gif -

vinyldeck Tuesday, July 17, 2012 11:49:30 AM

I have this showing now as Current browser.js status: enabled.
Target version and time stamp of the active browser.js file is Opera Desktop 11.62 core 2.10.229, July 17, 2012. Active patches: 231 .

But the thing is it didn't work by searching for it and placing it in the Opera directory, it only seems to work for me by downloading Opera 12.00 which doesn't actually load because of my operating system, but this seems to update the javascript file, the only thing I have noticed however is that when I open up my twitter homepage it takes a little while for the left hand tweet box to show, but once it has it works.

Is there any way to make this all load fast like it did prior to this js update?

ClashCityRockerclashcityrocker Tuesday, July 17, 2012 1:03:48 PM

Originally posted by Vinyl.Deck:

Can we get a new js patch for Opera 11.64?



Nope, 12 is now the stable Opera.

if you try and force a 12 browser.js, who knows what other patched sites will break as a result of the differences between the way 11.6 and 12 work.

It's really not a good idea. What would be better, and really the only safe fix, would be to pull out the fix and put it into a user.js patch.

You would have to ask, what is the point, nobody should be on 11.6x anymore, as it's not getting security fixes either.

Swapnil RustagiSwapnil99pro Tuesday, July 17, 2012 1:14:35 PM

Originally posted by clashcityrocker:

Nope, 12 is now the stable Opera.


However, Opera 11.64 is still supported for BrowserJS updates.
And, it should be supported atleast till Opera 12.00 makes it into the Mac App Store. Because the next update to Mac App Store would be Opera 11.65, Opera will need to provide BrowserJS updates for it. Opera 11.65 and 11.64 use the exactly same Core, so just get the 11.65 BrowserJS update and place it into 11.64's Opera directory, renamed to browser.js (complete file name with extension).

vinyldeck Tuesday, July 17, 2012 2:03:49 PM

Well all I can say is that I have the up-to-date javascript working on 11.64 with Twitter.

If that was the case about it being forced then why is it being accepted on 11.64 in the first place?

Ola P. Kleivenolak Tuesday, July 17, 2012 2:07:11 PM

We still release browser.js for 11.5x, 11.6x and 12 every week (when 12.50 comes along we'll probably do 11.5x less frequently) and updating is automatic, but Opera checks only every three days. We don't recommend going through all the hoops described above unless something is wrong with your install. Help->Check for updates should be enough in 99.9% of cases.

vinyldeck Tuesday, July 17, 2012 2:07:41 PM

Originally posted by clashcityrocker:

Originally posted by Vinyl.Deck:

Can we get a new js patch for Opera 11.64?



Nope, 12 is now the stable Opera.

if you try and force a 12 browser.js, who knows what other patched sites will break as a result of the differences between the way 11.6 and 12 work.

It's really not a good idea. What would be better, and really the only safe fix, would be to pull out the fix and put it into a user.js patch.

You would have to ask, what is the point, nobody should be on 11.6x anymore, as it's not getting security fixes either.

The point being that some people use the older browser due to compatibility with their operating system, not everyone has the most up-to-date system. Oh and the new javascript loaded for 11.64 when I attempted to upgrade to 12.00 which failed but it still updated the .js it would appear.

Charles SchlossChas4 Tuesday, July 17, 2012 2:18:38 PM

Target version and time stamp of the active browser.js file is Opera Desktop 12.00 core 2.10.289, July 17, 2012. Active patches: 218 .

Also at least in the US Mac app store the Opera update is not live yet (11.65)

vinyldeck Tuesday, July 17, 2012 2:28:50 PM

Is this what you'd expect to be seeing for the Opera 11.64 browser?

Current browser.js status: enabled.
Target version and time stamp of the active browser.js file is Opera Desktop 11.62 core 2.10.229, July 17, 2012. Active patches: 231 .

Ola P. Kleivenolak Tuesday, July 17, 2012 2:54:32 PM

Yes

Samed Ayanagresiff Tuesday, July 17, 2012 3:12:48 PM

up

ChrisCjcr Tuesday, July 17, 2012 3:43:39 PM

Seems the problem is now fixed by Twitter side, right? for me now works again without browserjs fix (disabled here).

Swapnil RustagiSwapnil99pro Tuesday, July 17, 2012 3:59:12 PM

Originally posted by Chas4:

Also at least in the US Mac app store the Opera update is not live yet (11.65)


I never said it was. But Opera 11.64/65 would be supported for BrowserJS updates atleast till end of the year - by which, then, there should be "stable" (from other's perspective who think 12.00 is not stable; I am happy with 12.00) versions of Opera, so that people stuck on 11.64 can move ahead. Yeah, I know some will be stuck on 11.64 for a long time before they have found a reliable, good alternative to Unite.

netwolf Tuesday, July 17, 2012 4:26:24 PM

Originally posted by olak:

Help->Check for updates should be enough in 99.9% of cases.


That didn't work at all with my main install (11.64).
I've been trying more than just a few times (and also had some update notifications which I didn't ask for).

Until today, I had the .js file from June 11th (more than 4 weeks old!), and I only got the new one after manually downloading the file and replacing the outdated one.

Looks like the updated .js file is not downloaded if you decline the client update...

Originally posted by Swapnil99pro:

Not even after following those instructions above?


Yes, it did, but only this procedure helped, not the "normal" way of using "Help - Check for new version...".
(and without going into further discussions, all 12.x build so far are a catastrophy when it comes to responsiveness and stability compared to 11.64 on the 3 systems I privatly manage; so I guess I'll stick with 11.64 for quite some more time...)

vinyldeck Tuesday, July 17, 2012 5:20:59 PM

Originally posted by netwolf:

Looks like the updated .js file is not downloaded if you decline the client update



I didn't decline the update to 12.00, and although it looked like it was going to update when I restarted the browser it was still showing as 11.64 version, but the thing is the javascript appears to have been updated because Twitter worked normally.

Do you have this when you check the javascript version on your Opera browser?

Current browser.js status: enabled.
Target version and time stamp of the active browser.js file is Opera Desktop 11.62 core 2.10.229, July 17, 2012. Active patches: 231

Here is how to check and report back.

http://www.opera.com/docs/browserjs/

Galileo Tuesday, July 17, 2012 5:35:48 PM

Originally posted by Cjcr:

Seems the problem is now fixed by Twitter side, right? for me now works again without browserjs fix (disabled here).


Disabled browserjs in a clean install (12.50) and twitter seems to work ok, can't any errors about the problem in error console.

Hallvord R. M. Steenhallvors Wednesday, July 18, 2012 1:06:07 AM

Originally posted by Galileo:

can't any errors about the problem in error console.



Confirmed - Twitter fixed it on their side too. Nice speed! :-D

Çağlar Yeşilyurtgreench Wednesday, July 18, 2012 10:05:54 PM

Hi Ola,

What is your opinion about DSK-370302? In forum, there is a topic, http://my.opera.com/community/forums/topic.dml?id=1480922.

Ola P. Kleivenolak Thursday, July 19, 2012 8:30:53 AM

It's a bug wink Will be properly fixed in 12.50, will look into solutions for current versions.

Charles SchlossChas4 Monday, July 30, 2012 3:26:01 PM

one for browserjs http://www.brookstone.com/static/customerService.jsp?panelId=400001 the hours for cherry creek store are hidden under the page

Charles SchlossChas4 Tuesday, July 31, 2012 7:21:48 PM

how is the outlook? new outlook (hotmail replacement coming) is not working at all in Opera

Çağlar Yeşilyurtgreench Tuesday, July 31, 2012 10:22:31 PM

Originally posted by Chas4:

how is the outlook? new outlook (hotmail replacement coming) is not working at all in Opera


I tried to use outlook.com (new hotmail) on Opera, Opera fails. Compose button does not operate. However, I think hotmail browserjs patches are required in order that hotmail is working well on Opera.

Charles SchlossChas4 Tuesday, July 31, 2012 10:57:59 PM

What I found strange is that if I ID or mask as Firefox on outlook, it is sent to the mobile version

Charles SchlossChas4 Thursday, August 2, 2012 2:12:35 PM

Target version and time stamp of the active browser.js file is Opera Desktop 12.01 core 2.10.289, August 1, 2012. Active patches: 223 .

The outlook is looking good wink

Write a comment

New comments have been disabled for this post.