google-code-export / wiquery

Automatically exported from code.google.com/p/wiquery
MIT License
1 stars 1 forks source link

Set Resource Type for Generated Scripts #151

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
One of my components adds some Dialogs to the page, which means that there is a 
generated JavaScript file fed down to the browser.  Apparently it doesn't have 
a resource type set when it is transferred, as Chrome loves to complain:

Resource interpreted as script but transferred with MIME type text/plain.

Original issue reported on code.google.com by michael.laccetti on 17 Jan 2011 at 5:03

GoogleCodeExporter commented 9 years ago
Will see if adding the resource types is an easy task.

Original comment by hielke.hoeve on 18 Jan 2011 at 2:03

GoogleCodeExporter commented 9 years ago
Michael,

Which wiquery version are you using? As far as I can see all js resources in 
wiquery 1.2 are typed.

Original comment by hielke.hoeve on 18 Jan 2011 at 2:20

GoogleCodeExporter commented 9 years ago

Original comment by hielke.hoeve on 18 Jan 2011 at 2:42

GoogleCodeExporter commented 9 years ago

Original comment by hielke.hoeve on 18 Jan 2011 at 2:51

GoogleCodeExporter commented 9 years ago
This is for 1.1.2 - I didn't realize that 1.2 had been released.

Original comment by michael.laccetti on 18 Jan 2011 at 3:48

GoogleCodeExporter commented 9 years ago
I'm getting the same issue.  And there is no WiQuery 1.2... are you referring 
to WiQuery 1.1.2?

Any workarounds?

Original comment by cdmc...@gmail.com on 20 Jan 2011 at 4:11

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Sorry I meant 1.1.2. A 1.2 version will be released soon. Currently there is no 
workaround.

I can't reproduce this, I am not using Dialogs so I can't confirm it either...

Original comment by hielke.hoeve on 21 Jan 2011 at 3:52

GoogleCodeExporter commented 9 years ago
I don't think it matters if you use a Dialog, but you need to use a component 
that injects JS on the fly.

Original comment by michael.laccetti on 21 Jan 2011 at 3:59

GoogleCodeExporter commented 9 years ago
Will install Chrome to see what you see. I assume the problem is reported in 
the Developers Tools?

Original comment by hielke.hoeve on 21 Jan 2011 at 4:14

GoogleCodeExporter commented 9 years ago
Yeah, it'll show up in the console.

Original comment by michael.laccetti on 21 Jan 2011 at 4:16

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I got a warning as well. Will look into it.

Original comment by hielke.hoeve on 21 Jan 2011 at 4:21

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
added the mimetype "text/javascript". Commited the fix on 1.1 branch. A release 
will come soon.

Original comment by hielke.hoeve on 21 Jan 2011 at 4:32