For a fun project, I've been implementing a small thumbnail page on a website that provides a specially catered view for the small site previews on New Tab pages. The end goal being to present the relevant information to the user before they ever need to visit the site. (Example: a weather site frequently visited, having a thumbnail page showing today's weather, so that the user can see the relevant information at a glance).
Opera this is by detecting
X-Purpose: preview
Likewise, Safari uses the same header, but requires additional JS to maintain a consistent thumbnail.
//On primary page
if (window.navigator.loadPurpose === 'preview') { /* go to thumbnail page */ }
//On thumbnail page
if (window.navigator.loadPurpose !== 'preview') { /* return to main page */ }
I'm curious if it's possible to duplicate this effect in Chrome or Firefox (the new speed dial available in the Aurora builds)?
Note: The X-Purpose: preview header in Chrome about 2 releases ago was a bug that was intended to be X-Purpose: instant and does not serve this purpose.
As far as I can tell, both Chrome and Firefox Speed-dial thumbnails are only populated when you visit a page - i.e. they're taken from the normal browsing context, with normal headers, rather than being independently queries in their own right.
You can test this a number of ways - I haven't spent long testing it, and you may have different version(s) of Firefox/Chrome than I do so you may see different results.
In Chrome - pin a tab or two in Speed-dial and then empty your browser history. The thumbnails should disappear until you re-visit the pinned page.
In Firefox - the above works, but you can also try out thumbnail generation directly using the moz-page-thumb:// URL protocol:
moz-page-thumb://thumbnail?url=http%3A%2F%2Fstackoverflow.com%2Fq%2F10369905%2F210865"
(please do test in whatever versions you're running as I'm curious about this question too - my research sofar is disappointing, but possibly in future ...)
Other references:
Original bugzilla entry for adding thumbnails to FF Speed-dial
Another bugzilla entry on fixing thumbnail protocol security issues
Related Super User question
Try using the speed Dial addon on Firefox, works really well.
It has features like bookmarks back-up and you can add a large number of bookmarks customizing each bookmark-tab.
link to speed dial for firefox
link to speed dial for chrome
Related
Wikipedia is a useful source of info but is less effective without images.
Due to security measures, modern browsers (latest updates of Firefox/Chrome/Safari) are not showing images which have origin different from that of host. eg: wikipedia.org page content is hosted on en.wikipedia.org but the media are hosted on upload.wikimedia.org, so the browsers are blocking all images.
I tried turning off browser security settings, adding wikipedia as exception, turning off https only requirement, altering site permissions, viewing on android wikipedia app (yes, even this fails as it can be a webview, thus using chrome browser internally to display content), etc. but to no avail.
What could be done to view the images on wikipedia?
Update: This issue has been resolved automatically (probably by wikimedia).
hey guys i am having a problem that i see others with online but i am yet to find a fix for my website.
facebook not detecting my images as of a couple of hours ago, i tried disabling hotlinks in cloudflare, tried fb debuger and scrapping tool etc no solution.
example if you try to share this page, no picture appears: http://www.yardhype.com/12-year-old-jamaican-girl-wins-master-chef-junior-competition/
ERROR message
"Provided og:image URL, ........testsite/wblob/5433A6CF57A599/2803/3DF62/w3l6_ERf2C3ADvxqhgccQg/jasmin.png could not be downloaded because it exceeded the maximum allowed sized of 8Mb."
the image is not over 8mb
ALso correct url is shown in the raw tag area
When I opened that link http://www.yardhype.com/12-year-old-jamaican-girl-wins-master-chef-junior-competition/ I don't see the image regardless; I opened up Chrome's debugger and saw this:
A Parser-blocking, cross site (i.e. different eTLD+1) script,
http://ajax.cloudflare.com/cdn-cgi/nexp/dok3v=85b614c0f6/cloudflare.min.js,
is invoked via document.write. The network request for this script MAY be
blocked by the browser in this or a future page load due to poor network
connectivity. If blocked in this page load, it will be confirmed in a
subsequent console message.See
https://www.chromestatus.com/feature/5718547946799104 for more details.
So the way that page is displaying the image is likely not up to standards.
I am using the Navigation Timing API to get real user performance data for visitors to my company's site. I am looking at visitors who use Chrome, Firefox, and IE 9+ and focusing on two main matrices of measurement:
Page Load => (loadEventEnd - navigationStart) and
Interactive => (domInteractive - navigationStart)
I have gathered a lot of data and have noticed something unexpected, IE9+ has lower page load and interactive times than chrome and firefox. Has anyone else experienced this? Does IE set the navigation timing events differently than Chrome and/or Firefox? From all the performance sites I have looked at Chrome and Firefox should be much faster at loading pages than IE. I have looked over my code and tested dozens of time to ensure I am capturing data from the API correctly and appropriately storing it in my DB. Any thoughts?
I have a webpage where the user has the possibility to display the terms and conditions without reloading the page, via AJAX. That, in itself, is no problem, however, I am also trying to push a history state.
That works fine in most browsers, except in IE. For some inexplicable reason, there, the content is loaded via AJAX, but also, a new tab is opened with the previous page. How can I fix this?
You can see the example on this webpage ( http://galaxy-battle.de ), try clicking on "T&Cs" in the "Join"-box.
IE9 and below doesn't support pushState. You have an exception when calling the following line
window.history.pushState(null, null, pathFullPage);
SCRIPT438: Object doesn't support property or method 'pushState'
?terms_and_conditions, line 62 character 21
You may probably be interesting looking on some workarounds discussed at Emulate/polyfill history.pushstate() in IE
Old but still current question. I just want to say I would recommend not to try to emulate pushState on IE.
Instead of that, you can use a feature detection :
if history.pushState is not null (browser supports pushState), you use it and load your content with nifty javascript
if history.pushState is null (browser does not support pushState), you change url / follow the link and make a full page change
Of course, this means IE<=9 users won't have all the cool animations other users have. But the question I want to ask is : do you want to see on the net links to your website containing # ?
Users may think your app is useful and paste links to it on the web. That's cool, because it brings you some google juice. Now, if that user uses IE and you use history.js, user will paste a link containing a hash.
This will defeats proper indexation of public pages of your app, and also will look ugly. My personal opinion is that having a js animation or lightbox for IE users doesn't worth those trade off.
I have an application that I'm targeting a wide variety of devices and platforms. The application can render different HTML based upon the type of client. However due to the complexity of the application, it shares a considerable amount of JavaScript libraries that rely on a number of async and ajax method calls.
One of the targets for the application is Opera Mini. This "sort-of" works but it seems like sometimes when building up the specialized markup to send down to the Opera Mini JVM client it does not wait until the async calls are complete. Are there any techniques or tools to see what's going on with the Opera Server (not my application web server) Side processing of the page to determine what I can do to make this solid?
It would appear that after further investigation that the server side browser is fairly picky when it comes to CSS. I can't remember the exact problem, but as soon as I removed the stylesheet all content was displayed properly. At that point I slowly re-introduced the CSS and everythning came back online and worked as expected.
Your javascript will only be allowed a short time before it is aborted:
JavaScript running on the Mini server
will only run for a couple of seconds
before pausing, for resource
constraint reasons. This applies to
JavaScript run due to an event firing
e.g. onload, as well as code run
because of a user action.
~ http://dev.opera.com/articles/view/opera-mini-web-content-authoring-guidelines/#javascript
So the best would be to serve the least javascripty version of your site to the Opera Mini user-agent.
You can type server:source in the address bar once a page is loaded if you want to see the current DOM tree.
It's also possible to post that source to a script on your server using server:source?post=http://your.server.com/script. It will send three fields as a POST request: url, host and html. You can then make your script save it to a file.
(Answering an old question in case it helps someone.)