[9.0] Failed to read the 'rules' property from 'CSSStyleSheet':

[thomas15v]

Impacted versions:

• 9.0
• Other odoo versions also act weird if you right click on a menu (tested community).

Steps to reproduce:

• In google chrome try to open your user preferences. Firefox does not seem to be impacted.
• Trying to edit any model
• Sometimes happens with wizards

Video/Screenshot link (optional):

[Yenthe666]

Hi @thomas15v,

Thanks a lot for your report.
I've just tried this on the latest Odoo 9 (community) on Chrome and Firefox and it seems to work fine.
Can you reproduce it on an official test instance (runbot.odoo.com)
Do you have custom plugins added that modify CSS?
Is your Odoo on the latest source code?
Which version of Chrome are you using?

Regards,
Yenthe

[thomas15v]

Forgot to mention that you need Chrome 64.0.3282.119 akka the latest version. Updated rolled in yesterday. Screenshot is from runbot.

[Yenthe666]

Seems to work fine at my end. CC @ged-odoo as it is JS related.

[thomas15v]

Just tried with a fresh google chrome without any addons, same problem. I actually knew about this bug a while longer since I use chrome beta, but I didn't thought it would make it to the stable version.

Also we have this error on every odoo version, when right clicking a link (menuitem in community).
.
I am not sure if they are related, but since it is happening with the same chrome version I think it might.

[cmarrero]

I can confirm the error with chrome 64

[jakubhruby]

#metoo
on ArchLinux
Firefox has not this problem

[Yenthe666]

Yep, got it too now:

[ged-odoo]

this is interesting. Yesterday, I had the crash (the one with the addeventlistener), in chrome 63. I thought we broke odoo, i tested on different versions. Then, I thought it could be related to extensions, so I disabled all my chrome extensions (just 4 or 5, not a big user of extensions), and restarted chrome. The problem disappeared.

[ged-odoo]

difficult to say, but my first guess is that the addeventlistener crash is related to chrome, not odoo's code. However, I don't know for the other crash with cssstylesheet.

[ged-odoo]

does it happen for version 10/11?

[thomas15v]

• cssstylesheet: Only odoo 9
• Eventlister: On all versions (but I can't make it happen again since today, probably the extension that caused it is updated)

[traviswaelbro]

Also having this problem on version 9. Confirmed to happen when trying to "Send by Email" on Invoices with Chrome v64.0.3282.119.

[aek]

Seems that basically, the issue is related to an empty CSS stylesheet introduced dynamically here:
https://github.com/odoo/odoo/blob/9.0/addons/mail/static/src/js/announcement.js#L16
in the format of:

_ab_location: function(dbuuid) {
    return _.str.sprintf('https://services.openerp.com/openerp-enterprise/ab/css/%s.css', dbuuid);
},

That js file does not introduce any useful feature for clients and it's returning an empty response - at least for non-enterprise database uuid - it's causing this issue with the chrome 64. That js file or the code it contains was removed for new versions of Odoo. Mostly that's the reason that you couldn't reproduce it in new versions

Still could be helpful to better catch the error here:
https://github.com/odoo/odoo/blob/9.0/addons/web_editor/static/src/js/transcoder.js#L16
to avoid this situation in the future

The most simple solution could be that Odoo S.A fix the CSS response of that file to at least one CSS Rule for that Ghost file
Another one could be simple extend (or manually find) the view record for mail assets to remove the line:
<script type="text/javascript" src="/mail/static/src/js/announcement.js"/>
Like this:

<template id="mail_assets_backend" name="mail assets" inherit_id="mail.assets_backend">
    <xpath expr="//script[@src='/mail/static/src/js/announcement.js']" position="replace"/>
</template>

I have tested that template extension to remove the inclusion of the announcement.js file and it seems like solving the issue at least in the detected scenario of the empty CSS file.

Talking about the solution for web_editor/static/src/js/transcoder.js you will need to remove the load of the original file and replace it with your fixed version. But I think that it won't be necessary if the previous patch fix completely the situation

Best Regards

[KottmannM]

I have the same problem with odoo 9 enterprise.

[wim-a]

We also have the same problem with Odoo 9 Enterprise.

[jithinkr12345]

Do we got any fix for this issue??? @Yenthe666

[MouTio]

It appears that the property "rules" is missing in the CSS resource and in Firefox is treated as a warning, but in Chrome is treated as an exception.

If you show the console of both browsers, you will see the messages.
Try to enter to "Preferences" or to edit a random user.

This is the error shown by Firefox console in runbot:
Can't read the css rules of: https://services.openerp.com/openerp-enterprise/ab/css/ddf53f40-028e-11e8-ab9c-a4bf011da6d8.css

[MouTio]

Okay, the solution is to change the code of transcoder.js located in web_editor/static/src/js:

The property "rules" is not well checked.

This line is wrong (around line number 16):
if (sheets[i].rules) {

It has to be changed to this:
if (sheets[i].hasOwnProperty('rules')) {

and the code will work fine in Chrome browser too.

I have created a PR.

Please, verify it, @Yenthe666 @ged-odoo

[wim-a]

I installed this fix. Works fine. Thanks a lot.

[ThomasBinsfeld]

Same issue. @MouTio fix seems to work fine 👍

[Yenthe666]

My co-worker created an official ticket for this with the number 813371

[MouTio]

@Yenthe666 What is an 'official ticket'?
Is it the same as PR?
I created my first PR to fix this bug:

#22603

[Yenthe666]

@MouTio an official bug report is one reported through odoo.com/help with your enterprise license key. It means that the issue moves up the list and gets a high(er) rating.

[remi-filament]

I have the same issue on Odoo CE v10 - I have created PR #22679 to address this issue on v10

[treviser]

I have the same issue on Odoo CE v11

[gmarcon]

Same issue with Odoo CE 10.0-20171227 and Chrome 66.0.3359.181 (Official Build) (64-bit)

Manually applying https://github.com/odoo/odoo/pull/22679/files fixes the issue

[determin1st]

You can also put it in try...catch block to suppress browser warning and check that .rules property

[Yenthe666]

@gmarcon that is quite a long while without updating an Odoo too though 😉

[determin1st]

i dont even know what odoo is! just stucked in this notification. how to get out) backend is over, forget it! the future is for browser side

[jpaulin]

@ged-odoo I had similar error in Chrome with Odoo 10. Came down to removing a extension called Loom (video record / screen cap extension). When Loom was removed, Odoo no longer crashed.

[easternwawoman]

In case a noob arrives here, I fixed this prob in latest ver. Chrome by: (1) uninstalling and reinstalling LiveStyle ext in Chrome and then (2) disabling all extensions excet for LiveStyle. The reinstall had no effect, based on usage. Disabling extensions did create the change. I have not turned all ext. back on so I have not pinpointed the conflict. I did turn Google Voice on; no problem. The other extensions were: Full page Screen Capture, CaptureCast; Checker5 Plus; Cryptonite MetaCert, Onetab and the WavesLiteApp. Will update if I pinpoint the extension that created the conflict. And BTW, while I'm not a noob, I'm only dreaming of becoming a developer. :-)

[cierek]

Are you sure you are running the latest release? I have customers running on Odoo 9 and 11 without any error since the update

[easternwawoman]

As I said in my post, I uninstalled and then reinstalled -- that reinstall was the download of latest version. I also have the latest ver. of Chrome. While it's now syncing fine betwn Ch. browser and my IDE, it is still throwing the css files not found error: " Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules. " I have turned back on extensions G. Voice, Checker Plus for GMail, and CSS Peeper with no impact. Do need to turn on MetaCert and will test later on.

[pedrobaeza]

Better to start from a fresh DB.

[easternwawoman]

local server db, you mean? If so, I use ServerPress's DesktopServer which has a unique localhost domain ...eg... dev.cc is what we use. Could that be creating a conflict? I wouldn't think so but ? And I had DServer create a new site yesterday afternoon after the extension change -- that's the site I'm working on this morning is throwing the error. I checked other local sites here and they do the same. Sheesh recreating db for 6 localhosted sites here would be a royal PIA ...and a hit of nonbillable time... :-(

…

On Thu, Aug 16, 2018 at 8:43 AM Pedro M. Baeza ***@***.***> wrote: Better to start from a fresh DB. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#22517 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACrM0wc4fbyg_S6uoLEgvHvjqLLZEmfrks5uRZMIgaJpZM4RswoV> .

[pedrobaeza]

Well, I'm suggesting a method to try to debug the problem. First, to see if in a fresh DB, there's no problem. If so, then the problem is in the data inside the DB, and you get a way to work on.

[traviswaelbro]

Alternatively, if this is only an issue on your local setup, you should be able to just use Firefox and not have any issue. At least in my experience with this issue, the problem only happens in Chrome.

[easternwawoman]

Thanks for the help. I'm not clear on why a fresh DB yesterday would be any different from one today. The CSS style error has been occurring for some time with other local sites. I just stopped using LiveStyle. Retried recently when there was some time. The extensions disabled caused it LiveS to work again. I had ServerPress deploy a new site yesterday afternoon after the extension disable on the other site caused LiveS to work. That SP deployment does create a new DB. Style error persisted but LiveS does the updating betwn browser and Sublime. So, it's usable/does what I need it to do despite this: *Error in event handler for runtime.onMessage: SecurityError: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules at findStyleSheets (chrome-extension://diebikgmpmeppiilkaijjbdgciafajmg/scripts/content-script.js:1014:12) at chrome-extension://diebikgmpmeppiilkaijjbdgciafajmg/scripts/content-script.js:1052:13* Anyway, I think I'll just use this as it is and over time start looking at what else is available. I'm sinking in quicksand here from crazy workload; the ROI from fussing with it is a business expense that's not worth it. If I do find some free time..maybe I'll fuss with it. Dunno. Just wanted to report this here. I greatly appreciate you reaching out and taking from your time a moment to help. It's really been a sweet tool.

…

On Thu, Aug 16, 2018 at 8:58 AM Pedro M. Baeza ***@***.***> wrote: Well, I'm suggesting a method to try to debug the problem. First, to see if in a fresh DB, there's no problem. If so, then the problem is in the data inside the DB, and you get a way to work on. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#22517 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACrM08cq2LUkUpLQr1y9ERt-8cXpXo__ks5uRZa3gaJpZM4RswoV> .

[easternwawoman]

TY.. will keep that in mind. I don't like doing dev work in Firefox but that's good to know. Have a great day!

…

On Thu, Aug 16, 2018 at 9:09 AM Travis Waelbroeck ***@***.***> wrote: Alternatively, if this is only an issue on your local setup, you should be able to just use Firefox and not have any issue. At least in my experience with this issue, the problem only happens in Chrome. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#22517 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACrM0zCwY7md1O-Pf2G9zQemz3vSr7W2ks5uRZktgaJpZM4RswoV> .