What's happening with the Google O3D WebGL wrapper? - html

I am not seeing any updates for Google O3D WebGL wrapper for a very long time, and I am not seeing much in the form of posts regarding o3d webgl on this site or other content on the internet - what's happening with O3D WebGL wrapper is it still in development?

Its actively maintained inside of Chrome also see The future of O3D blog post in Chromium blog.

Related

Altering my web site's Firefox New Tab page tile

I opened up Firefox this morning and was presented with the "New Tab" page. One of the tiles that appeared on this page was Mozilla's MDN site.
Unlike all the other tiles (which were merely screenshots of the web site), the MDN tile has a custom tile which advertised the MDN.
Looking at the HTML source for MDN I couldn't see any META or LINK tags that would suggest how they are achieving this?
I've Googled around but can't see any documentation about how I would go about customizing tiles for my own web sites so they display as pretty as MDN on this page..?
I was wondering if there was a standard mark-up for this so it would also work with Google Chrome's equivalent start page?
Looking on the Mozilla help page for Firefox users, you can see that tiles in their screenshots are not merely screenshots, but where can I see the web designer documentation for this..?
This is not under the control of the site.
See this bugzilla ticket:
Can a website specify their own enhanced tiles via some meta tag?
Right now no. There's been discussions around that, but there's
initially some worse privacy aspects where Firefox would need to
connect to a site to get that information potentially triggering
cookies similar to bug 1037673.
How enhanced tiles are implemented is the content comes from
cookieless https requests to mozilla servers, so there's lower privacy
risks of some types of tracking.
Another ticket has been opened requesting the feature.
You would need to make a deal with Mozilla to get special treatment for your site on their servers.

chrome canvas inspector 2015

I used this nifty feature that chrome had for quite a while called "canvas inspector". It was an experimental dev feature that had to manually be enabled.
It was quite helpful when working with webgl via something like THREE.js where you can easily create a bunch of undesired draw calls by accident.
Also, it worked on any website, you could simply take a snapshot and see whats going on in the canvas.
It... miraculously disappeared one day, and google does not give any insight.
I've tried some extensions but they dont feel nearly as good, or i couldn't even get them to work. Is there another way to get this back into chrome?
Apparently it was doing some cheeky stuff that they didn't want in the main project so it was removed in this issue: DevTools: make Canvas profiler an extension
We can make it an extension though. This bug is for tracking removal of the canvas profiler from the DevTools. There will be a separate initiative of porting the code being removed into github and publishing it as a Chrome extension.
According to that issue they might move it to an extension in the future but I haven't found any traces of it as of now. They haven't responded to a question in the above issue about where the new issue could be tracked.
Chrome and Firefox have both removed their Canvas inspectors...
Original Answer:
This is not exactly what the question asks for, but Firefox has a canvas inspector integrated:
https://hacks.mozilla.org/2014/03/introducing-the-canvas-debugger-in-firefox-developer-tools/
You can enable it in the settings of the normal inspector
EDIT: (2019)
The Canvas Inspector has been removed as of Firefox 67:
Mozilla deprecated listing
Bug report with reasoning
Alternative:
spector.js - Recommended alternative by Mozilla
Canvas inspection was just removed!
You can download an old version of Chromium here like Chromium_OSX_43.0.2357.81.dmg. (Provided by freesmug)
Happy Canvas Inspection!
This is the best extension inspector I’ve seen so far.
https://spector.babylonjs.com
First go into
chrome://flags
Then enable
Developer Tools experiments
Then after restarting your browser, open the devlopers tools by hitting f12, then in the top right corner is a gear. Click on it, go to experiments, then find "canvas inspection". It's unstable, but usable.

WebGL in Chrome works second time but not first time

WebGL does not work in the following three scenarios:
(for the 'test webgl' site used get.webgl.org)
1 Start chrome, Google search for the 'test webgl' site, click on the link in the search result.
2 Go to the 'test webgl' site from a link in an email.
3 Start Chrome from a short cut or command prompt, "C:\Program Files\Google\Chrome\Application\chrome.exe" http://get.webgl.org/
This only happens when Chrome is not already running. In other words WebGL does not work when chrome starts up. However it does work if chrome is already running.
The best demonstration is scenario number 3, above. This starts chrome and goes to http://get.webgl.org/ and Webgl does not work. Then do exactly the same again but this time with chrome already open and Webgl works.
Would very much appreciate feedback or a solution, thanks.
Have also created various test sites in html, javascript and webgl, in order to find a work-around. For example if webgl is not available then allow the user to click on a link to open the page in a new tab, this does not work. However if the user opens a new tab then loads the page, webgl is detected and works.
In short, if a customer opens chrome and searches for your website (that has webgl content). Then clicks on the link, webgl will not work. It does not seem reasonable to then instruct the customer to open a new tab and then go to the same website a second time. So far have not been able to find a solution so that it just works without the customer having to fiddle around.
I realize that this may be a chrome issue as it does not occur in firefox, however am trying to find a javascript solution rather than waiting for chrome developers to fix it.
Thanks for any suggestions.
(Windows XP Pro, Chrome V36)
Hi Mack,
Thanks for your reply. The majority of visitors to my web site have XP and Chrome. I should imagine that this is true for quite a lot of peoples, websites.
Problem 1 The first fallback I had on my website was to detect if webgl is supported. If yes then continue as normal. If no then display a help page. This was simple and worked, however, google crawlers do not handle the javascript very well, therefore always index the webgl help page, rather than the home page.
Solution 1 Managed to fix this by having a popup box appear when webgl is not supported, giving the user a choice of whether to continue or go to the help page. The conditional code that processes the user response is arranged so that if the user is a google crawler then it simply 'falls through' and displays the html content of the home page, and not the help page.
There are lots of web sites that seem to have this same problem, including get.webgl.org, in other words, if you do a google search for a website, and that site contains webgl detection and fallback code, the search result always shows the fallback content, rather than the authors intended main content.
Problem 2 Now that I finally have the home page listed correctly by google, found that am still losing many customers, as they are starting chrome, searching google for my site 'suit yourself shirts', clicking the link in the result and being told incorrectly that webgl is not supported.
Am very interested in your solution but do not quite understand how it works. Have tried detection then page refresh or load the page in a new tab or display a link for the user to load the page, but none of these methods seem to work. Seems like quite a fundamental problem that would effect many webgl websites. Would be very greatfull if you could explain your suggestion a little further. Thanks for your help, kind regards - Gary

capture screen areas

Is there a way to capture screen areas in the new packaged apps? Because of this Chrome bug http://code.google.com/p/chromium/issues/detail?id=68568&q=is%3Astarred&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20OS%20Area%20Feature%20Status%20Owner%20Summary users cannot download their SVG files as PNGs (vector-paint.com). I know there is the chrome.tabs.captureVisibleTab function but that is not accessible to packaged apps.
There is no way to do it now in the API, although I have reported this in a bug
In the meantime, you might want to try the workarounds described in this Eric Bidelman's HTML5Rocks post. I'm not sure if these options play well with CSP restrictions, though.

"This application does not support integration with your profile."

Past apps that I have built seem to work fine, but when trying integrate a simple HTML page embedded into an iframe, all I get is the above message ("This application does not support integration with your profile").
Any suggestions or direction helps.
Thanks!
It's possible that this question I asked previously might be useful.
Social Media sites preventing other sites displaying their pages in an iFrame