Can someone please tell me how to make an image saved in Data Folder an icon in Mozilla Add-on Builder.
I tried:
data = require('self').data
contentUrl : data.url(filename)
What did I do wrong?
Update
It worked well when the image is of type .png but for the type .ico . I really have no clue what happens in the background.
Can someone help??
I assume omitting the ;'s at the end of lines was also for intrigue.
I find that when the file is something other than a 16x16 .ico file, the add-on will be painfully slow and the mouse cursor will disappear. Maybe that's just a Linux thing, or something else peculiar to my setup.
Related
Im tring to understand why I can't print text on draw.io using Internet Explorer 11.
Basically what I do is creating a rectangle and double click on it to insert some text.
After that I go into [ File -> Print -> Preview ] , a new tab appears but the text is gone.
The debug shows nothing and there is no such error on Chrome , I really dont know what to do, hope someone can help me.
As this is not a development issue, it is better if you consult the website developers for a user support.
As an alternative, you can try to add the site to the compatibility view settings.
After that it will show you the text in print preview.
Note that adding this site to compatibility view list may create other issues.
Other way is to Export your drawing as an image or PDF using the Export option from this site.
It will export the drawing as it is than you can try to print it. It may help to solve your issue.
This is the exported image.
I don't believe this is a question suited for Stackoverflow as your best bet would be to contact the site developers.
I tried to find the answer to this problem - but had no luck finding it yet.
I moved a site to to the server. All is working fine - just the images are not showing up.
I know it is a (relative) path problem- but how to solve it??
If you are using chrome simple press f12 and look at the console tab, you should see some red errors stating that an image could not be loaded, then looking at the file path you can see what exactly is going wrong
Chrome console should look something like this
I'm having a bit of trouble using the retina.js script. I'm trying to swap the logo for a retina image on this page:
http://mikeleachcreative.co.uk/comps/fmp-mobile/
The script is included as instructed and there are definitely images included with the required '#2x' extension, you can view these images here to make sure:
http://mikeleachcreative.co.uk/comps/fmp-mobile/images/fmp_mobile_logo.png
add #2x onto the end of the filename to see the high-res version.
When this page is viewed on a retina device, I am still seeing the lower-res image, any help would be greatly appreciated.
Thanks.
It looks like (whenever the #2x image is checked) your server is returning 403 (not authorized). Check the settings on your server. Retina.js requires you to be able to make a HEAD request to the server (not GET or POST).
I'm making an app where i want to show the user a range of base64 encoded picture. They are shown by using data-url. If the user wants to save a picture, it can simply rightclick and save as (or drag it into a folder).
Are there any way to control the sugested filename? Right now Chrome just sugest "download" and doesn't even recognize it as an image. Can this be done in any way?
I only need it to work in Chrome.
Thanks for any help
Make sure you are setting the proper mime type for the image in the data uri. Doing this fixed the file extension in Chrome 17, for me. The file was downloaded as "download.png", and opened fine.
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUA
AAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO
9TXL0Y4OHwAAAABJRU5ErkJggg=="/>
However, if you really need full control over the filename, you can exploit the html5 "download" attribute of the a tag, to set the filename, and create a Blob object with your image data that will be used be downloaded.
See a demo here: http://updates.html5rocks.com/2011/08/Downloading-resources-in-HTML5-a-download
Read more here: http://dev.w3.org/2009/dap/file-system/file-writer.html
The current specification does not make this possible.
If you go to this site, you'll notice a big image in the middle.
If you inspect it, you'll see this.
<img src="http://s3.amazonaws.com/mosaicimages/hmn58067pa">
If you hover over it during Inspect mode, you'll see this:
img[480x640]
And that's normal. The picture should display.
But sometimes, when I browse my site, the image simply does not display. The HTMl is the same. Everything is the same. It's just that the "cache" messes up.
This is what it looks like: http://i52.tinypic.com/1190xu0.jpg
When the image doesn't display, I clear the cache in Chrome browser settings, and the image displays again. After browsing the site again, random pictures disappear.
It's weird because when you inspect it, the code is the same. However, the image says:
img[0x0]
That's very awkward, because the image really is there. it's in S3 and it's fine.
It happens on other pages as well, not just this page. It happens for all images that are in S3.
Some of you may not be able to reproduce it. Some of my friends reproduce it. but if you can, please help, thanks.
Edit: I found a few bug issues related to Chrome? Is this it?
http://code.google.com/p/chromium/issues/detail?id=67373&can=1&q=image%20304&colspec=ID%20Stars%20Pri%20Area%20Feature%20Type%20Status%20Summary%20Modified%20Owner%20Mstone%20OS
http://code.google.com/p/chromium/issues/detail?id=68622
Edit: everything works fine in incognito mode.
Do you get the following warning in the console?
Resource interpreted as [something] but transferred with MIME type [something else]
It may happen if an image is loaded dynamically (i.e. img src changed at runtime on the client) - which was nicely responded to here.
This could also be caused by the browser actually receiving an incorrect MIME type declaration - I don't imagine that would be an S3-specific issue (given the apparently wide range of similar problems encountered) and would rather suggest it could be an issue with a forwarding (corporate?) proxy etc. - this was the case for us when including fonts but never with images.
Google chrome has an excellent report issue located in the settings tab, take this issue to them,atleast they will rectify in future release chrome versions.