Sitepatching updates

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

Watch browser.js change on GitHub!

By Hallvord R. M. Steenhallvors. Thursday, January 19, 2012 9:45:09 AM

Ola has set up a browser.js repository on GitHub which we'll push future updates to. If you are interested in our site patching work (or just like reading obscure JavaScript hacks wink), go ahead and watch it!

c|net, GMail, ebayFacebook slow typing problems

Comments

Nimesh nimeshthakkar Thursday, January 19, 2012 7:11:41 PM

nice move up

MyOpera team, please fix this!fearphage Thursday, January 19, 2012 10:14:10 PM

Fantasdelicious!

Can i make a small suggestion? Please fix the formatting. 2 spaces always tabs, or whatever you're using, etc. etc. smile

I know browser.js is a combination of multiple files. Can you break that down on github (src folder) and put the completed ones in the dist folder?

Thanks again!

Hallvord R. M. Steenhallvors Thursday, January 19, 2012 11:11:37 PM

Yes, sorry about the formatting. We typically edit small fragments in whatever editor we prefer with its defaults, then paste said fragment into a TEXTAREA because the patches and meta data actually live in a database with a small web frontend. The script that puts relevant fragments together uses tabs for indentation, but isn't interested in being *very* clever since the output isn't really meant for (re-)editing.

Because of the DB solution it's not practical to put the individual patches on GitHub either. We may of course move away from this at some point and use Git to maintain the entire file. The current solution has some drawbacks, among them being it takes a bit of work to figure out who changed what and why. But IMO it works reasonably well.

Charles SchlossChas4 Friday, January 20, 2012 2:28:03 PM

Target version and time stamp of the active browser.js file is Opera Desktop 11.60 core 2.10.229, January 20, 2012. Active patches: 177 .

Hallvord R. M. Steenhallvors Friday, January 20, 2012 8:03:24 PM

Wow Charlie, you picked up the new version before I published the blog post to announce it :-)

Ola will update GitHub, I guess he will do it Monday. (The Facebook problem made us push this out in a hurry so we haven't done all the usual stuff yet).

Charles SchlossChas4 Friday, January 20, 2012 10:02:23 PM

bigsmile I was wondering about the Facebook being choppy, then I say a post on Twitter from a Opera person about it, and did a check for updates smile

Could a browserJS work for http://itunes.apple.com/us/app/iboostup/id484829041?mt=12 ? as the Mac App Store links don't redirect to the MAS, could do it only if the user agent is on 10.6.8 or 10.7.x

Jimtoyotabedzrock Sunday, January 22, 2012 2:11:40 AM

It's a shame Github can't fix their own CSS to work with Opera. mad

They can't fix it in part because they have sections of code duplicated

Ola P. Kleivenolak Monday, January 23, 2012 9:57:10 AM

Pushed to github.

MyOpera team, please fix this!fearphage Monday, January 23, 2012 6:48:27 PM

Originally posted by toyotabedzrock:

It's a shame Github can't fix their own CSS to work with Opera.

What's broken exactly?

Dan Alexandrudantesoft Sunday, January 29, 2012 12:42:56 AM

Source line numbering, for one.

MyOpera team, please fix this!fearphage Monday, January 30, 2012 8:13:43 PM

Originally posted by dantesoft:

Source line numbering, for one.

I don't know. It looks identical to Chromium 18 to me.

Jimtoyotabedzrock Wednesday, February 1, 2012 8:37:21 PM

Originally posted by fearphage:

Originally posted by toyotabedzrock:

It's a shame Github can't fix their own CSS to work with Opera.

What's broken exactly?



The gradients are all messed up because they repeated large sections of the css with the older pre Opera gradient code which ends up giving it solid colors in Opera.

And in css file highlighting for some reason -o- shows up as red.

Am I the only person who uses every browser enough to notice these things, lol?

Here is Firefox on the left, Opera 12 on the right.

http://files.myopera.com/toyotabedzrock/bugs/branch-all.png -

http://files.myopera.com/toyotabedzrock/bugs/url-all.png -

http://files.myopera.com/toyotabedzrock/bugs/watch-fork.png -

http://files.myopera.com/toyotabedzrock/bugs/zip-all.png -

The following is supposed to fade in:
http://files.myopera.com/toyotabedzrock/bugs/Transition-Opera.png -

There is some type of size error, not sure what it is, in this one.
You may have to zoom in to see what I'm talking about.
http://files.myopera.com/toyotabedzrock/bugs/watch.png -

Scroll down to .fade on this page to see the -o- error.
https://github.com/diaspora/diaspora/blob/master/public/stylesheets/interim-bootstrap.css

MyOpera team, please fix this!fearphage Wednesday, February 15, 2012 7:55:27 PM

I have to admit that I have to stare to see the difference in several of those. I hope they get them resolved though.

Also I've been unable to use opera for a while now. Infinite-crash-loop ftw.

Write a comment

New comments have been disabled for this post.