search

fantasycalendar / FoundryVTT-Tagger

Other
6 stars 4 forks source link

[VERY MINOR BUG] evidence of a difference in OPERA browser in interpreting css comments. #30

Open galaara98 opened 1 year ago

galaara98 commented 1 year ago

Describe the bug When loading foundry where tagger is an active module, and viewing the js console in OPERA BROWSERS right at User login (possibly only GM User, but probably all):

a debugger error is thrown in the console: blah blah blah: Could not load content for https://foundry.node.server/modules/tagger/style.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

in the file: tagger/style.css, in your module, there is a line /*# sourceMappingURL=style.css.map */

according to https://www.w3schools.com/css/css_comments.asp comments in css are:

/* sdfsdfsf */

OR 

/* This is
a multi-line
comment */

it would appear that in MOST browsers this rule is interpreted as /*sdfsdfsdf*/

but in OPERA based browsers, the white space is required..., so therefore the line in your module is not a comment, in Opera based browsers (it has extra characters, but the stupid browser still reads the sourceMappingURL statement)

Im not agreeing or disagreeing with how browsers want to be, but if you wouldn't mind, would you change the comment in your style.css file to be

/* # sourceMappingURL=style.css.map */