[11.60 & 12.00] Presto 2.10 bug - blacklisting of UserJS files - Beta testing (including snapshots and previews)

22. November 2011, 19:38:06

Behind the Mirror

Posts: 1178

[11.60 & 12.00] Presto 2.10 bug - blacklisting of UserJS files

I can confirm this issue for the two current snapshots - 11.60 (1159) and 12.00 (1116).
[Okay, there is 1163 out already, but I still don't have it running. I'll test it later.] Edit: confirmed for 1163 as well.

What it is, basically: if you have a running user script and by editing it on the fly, you introduce a syntax error in it, Opera will alert you via the Error Console and in Dragonfly (Scripts). So far so good, but if you then correct the errors in the file, Opera won't use it again during the same browsing session. A workaround is to rename the file and in this line of thought I observe the following behaviour: if at some point of the current session a .js file has been non-working, Opera won't use a file with that name until the next restart - kind of blacklisting these names, so just switching back and forth between two names does not work.

By the way, I apt to blame this on the new engine - Presto 2.10 vs. the older 2.9, as this issue doesn't exist in Opera 11.52, which is using 2.9 and Presto is the main difference between the two. Correct me if I'm wrong.

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

29. November 2011, 02:17:27

hallvors

Opera Software

Posts: 1778

Yes, this is extremely annoying :-/

--
My blog: miscoded
Stupid code from major websites uncovered and criticised
Contribute site fixes! - OTW&TA- all sites must work

29. November 2011, 11:06:36

D1sasterp1ece

Behind the Mirror

Posts: 1178

Oh, thanks for the feedback. That's not just someone confirming it, but an Opera employee

So is this a known bug? If not, I'll care to report it.

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

29. November 2011, 12:32:15

hallvors

Opera Software

Posts: 1778

It is a known bug and there should be a fix in the pipeline. I'll try to figure out if that fix got lost somewhere so thanks for nagging

--
My blog: miscoded
Stupid code from major websites uncovered and criticised
Contribute site fixes! - OTW&TA- all sites must work

29. November 2011, 12:48:33

D1sasterp1ece

Behind the Mirror

Posts: 1178

Thanks again then and let's hope for a fix before 11.60 final

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

6. December 2011, 12:23:04

D1sasterp1ece

Behind the Mirror

Posts: 1178

Sadly enough, this bug is still here in 11.60 final (1185).
I suppose I'll have to wait for the next Presto update

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

21. December 2011, 14:48:16 (edited)

jesus2099

♡.. \(^Δ^;)/ ..☭

Posts: 366

It's HORRIBLE BUG OMFG !
How are we supposed to do ?
I have one script that even if I reboot Opera, it’s still blacklisted ! (._.?)
I have to rename it, that’s crazy.

reported DSK-353919

edit : I just see that Opera employee aknowledged the bug in this thread.
Hopefully my EmEditor has the rename and save function handy but … wow, Have to wait for this very important fix though…

jesus2099 × Ti = Tristan + patate12 ÷ saucisson7 éditer bug report
※ My bugs and whishlist for Opera
Using Opéra v12.16 (1860) on oui-une-dose ikspé et sept

21. December 2011, 17:52:37

D1sasterp1ece

Behind the Mirror

Posts: 1178

Not glad that the bug's still here, but I'm glad at least that it's not just hallvors and me being aware of this bug. Furthermore, I didn't report the bug myself because he said it's a known one...
11.52 will be my main build for now.

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

3. January 2012, 18:09:52

hallvors

Opera Software

Posts: 1778

For my own reference mainly, it's CORE-43307.

Rejoice: It's been fixed (again), QA gave the fix a green light on December 18th and fix was integrated into Opera's core code on December 22nd.

--
My blog: miscoded
Stupid code from major websites uncovered and criticised
Contribute site fixes! - OTW&TA- all sites must work

4. January 2012, 05:51:33

Swapnil99pro

Posts: 1408

Originally posted by hallvors:

fix was integrated into Opera's core code on December 22nd.

So that means the next Opera 11.61 snapshot and it's succeeding Opera 12 snapshot are going to contain the fix for this issue?

Windows 7 SP1 x86 edition and Windows XP Service Pack 3.
If you need any help from me with regards to Opera, please make a comment on any of my blog posts.
Support Opera wishes

4. January 2012, 10:51:33

hallvors

Opera Software

Posts: 1778

11.61 probably won't, they probably add only security and stability fixes to 11.6x at this point. It will probably show up in a O12 snapshot shortly, when they have updated their core version.

--
My blog: miscoded
Stupid code from major websites uncovered and criticised
Contribute site fixes! - OTW&TA- all sites must work

11. January 2012, 09:35:51

Swapnil99pro

Posts: 1408

As expected, it is patched in Opera 11.61 build 1234. The changelog says -
CORE-42565 Crash on applying 3025 background images
CORE-43307 Do not cache invalid UserJS source files
CORE-42991 Stylesheet not applied due to malformed gzip content
...........................

Windows 7 SP1 x86 edition and Windows XP Service Pack 3.
If you need any help from me with regards to Opera, please make a comment on any of my blog posts.
Support Opera wishes

11. January 2012, 09:44:46

jesus2099

♡.. \(^Δ^;)/ ..☭

Posts: 366

I guess it’s a beta release as it is not proposed when I check for updates.
Do you know if CORE-43307 both resolves this « userjs blacklist » and « Sometimes I have to rename my userjs for Opera to run the new version of it » problems ?

jesus2099 × Ti = Tristan + patate12 ÷ saucisson7 éditer bug report
※ My bugs and whishlist for Opera
Using Opéra v12.16 (1860) on oui-une-dose ikspé et sept

11. January 2012, 10:29:34

hallvors

Opera Software

Posts: 1778

Great news for 11.61. And yes, it does fix those problems

--
My blog: miscoded
Stupid code from major websites uncovered and criticised
Contribute site fixes! - OTW&TA- all sites must work

12. January 2012, 17:32:03

D1sasterp1ece

Behind the Mirror

Posts: 1178

I still notice some inconsistency with this - sorry to say it, but it's like the bug isn't fully fixed.

It's related to the @include / @exclude filters in the .js files. What you can try, I think it's reproducible:

Set a UserJS directory for My Opera (in site preferences). In that dir, put a file with the following content:

// ==UserScript==
// @include *group*
// ==/UserScript==

alert("hello, world!");

... so it would match "http://my.opera.com/community/forums/group.dml?id=45961", the old-style view of the forum ("View all sub forums"). The first time you load the page, the alert will fire, but if then you change the include filter, say, to match any forum topic, e.g.

// @include *topic*

then the alert will still fire on the previous page ("View all sub forums") and not on a topic page (e.g. still matching *group* but not *topic*). But if you then rename the file, everything will be okay (similar to the workaround for any 11.6* build before 1234).

11.52 (1100) is all okay in this respect.

Please let me know if you can reproduce it or if I may be wrong with something.

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

12. January 2012, 17:35:05

jesus2099

♡.. \(^Δ^;)/ ..☭

Posts: 366

Yes it’s what I meant by « Sometimes I have to rename my userjs for Opera to run the new version of it ». When I change include/exclude stuff in userjs, I HAVE TO rename the userjs (and if I rename back, it reverts to old matching).

How comes you got a new version ? I’m in 11.60(1185) and if I check for new updates it says I do have got the latest version. (._.?)

jesus2099 × Ti = Tristan + patate12 ÷ saucisson7 éditer bug report
※ My bugs and whishlist for Opera
Using Opéra v12.16 (1860) on oui-une-dose ikspé et sept

12. January 2012, 18:25:25

D1sasterp1ece

Behind the Mirror

Posts: 1178

Originally posted by jesus2099:

Yes it’s what I meant by « Sometimes I have to rename my userjs for Opera to run the new version of it ». When I change include/exclude stuff in userjs, I HAVE TO rename the userjs (and if I rename back, it reverts to old matching).

How comes you got a new version ? I’m in 11.60(1185) and if I check for new updates it says I do have got the latest version. (._.?)

11.61 (1234) was posted on the Desktop Team blog. What you've got is the latest final version, it's by design that the updater shouldn't tell you about snapshots.

So long story short, the bug is fixed for the actual script, but still stands for the comment block (include/exclude/encoding etc.)

By the way, I also observe some inconsistency with the way the Error Console reports JS errors (again, compared to 11.52), but I couldn't find a reproducible way to make it happen.

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

13. January 2012, 09:12:30

hallvors

Opera Software

Posts: 1778

Originally posted by D1sasterp1ece:

the bug is fixed for the actual script, but still stands for the comment block (include/exclude/encoding etc.)

Hm, could you please file a follow-up bug report? It sounds like this problem has much lower priority, so I can only promise a quick fix if the developer who fixed the previous bug has a moment and knows what's wrong..

--
My blog: miscoded
Stupid code from major websites uncovered and criticised
Contribute site fixes! - OTW&TA- all sites must work

14. January 2012, 00:47:48

D1sasterp1ece

Behind the Mirror

Posts: 1178

Kay, reported it.
DSK-355247

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

9. February 2012, 14:39:45

alex-shpak

Русский Product Tester, Desktop Team

Posts: 397

Fixed in latest snapshot

How to write a perfect bug report / Как написать идеальный баг-репорт / History of the browser user-agent string
We are working on it / Мы работаем над этим

10. February 2012, 11:48:00

D1sasterp1ece

Behind the Mirror

Posts: 1178

Yeah, I saw that and I just tested it, I can confirm it's fixed now for 11.62 (1297) and I hope that this fix will soon be merged into the 12.00 branch as well.

Note to the mods: you may close this topic, I think that this case is over

А crappy old PC running XP Pro SP3 and Opera 11.64 (1403) + 12.02 (1578) + 12.16 (1860) (plus a few other builds)
Loyal Opera user saying NO to Opera 15.
Opera Mobile 16 & Opera Mobile 16 beta & Opera Mobile 12.1 & Opera Mini 7.5 on Samsung Galaxy Nexus
Opera Mobile 12 & Opera Mini 7 on Nokia E51

10. February 2012, 13:29:19

jesus2099

♡.. \(^Δ^;)/ ..☭

Posts: 366

I dare not install unstable versions as even the stable versions are in fact not so stable or regress.
I’m still waiting for current regressions (text area search, userjs blacklist, fonts unaligned, )scroll marker) to be fixed in a stable version and then later never upgrade again. Except if Opera eventually implements CSS RUBY support, 14 years after IE5beta2. :/

But I still love Opera so much !(I discover new great tricks, everyday). It’s just that I must now refrain from updating without good reason.

jesus2099 × Ti = Tristan + patate12 ÷ saucisson7 éditer bug report
※ My bugs and whishlist for Opera
Using Opéra v12.16 (1860) on oui-une-dose ikspé et sept

10. February 2012, 15:20:55

hallvors

Opera Software

Posts: 1778

Originally posted by jesus2099:

text area search

among my pet bugs too :-p

You know you can install unstable versions next to stable ones, and they will not interfere with each other as long as you make sure you install to a different folder?

--
My blog: miscoded
Stupid code from major websites uncovered and criticised
Contribute site fixes! - OTW&TA- all sites must work

The My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features

[11.60 & 12.00] Presto 2.10 bug - blacklisting of UserJS files

[11.60 & 12.00] Presto 2.10 bug - blacklisting of UserJS files