Any Idea on the new updates of chrome, where in when opening a web application game on Phaser, there is a huge performance drop and the PC(desktop) slow becoming sluggish.
We tried to convert all are renderer to canvas mode and it solve the problem. Any idea might it cause to WEBGL on Desktop. Does this issue related to the antivirus, we make use of semantic.
I had the same issue, I changed type 'AUTO' to 'CANVAS' in GameConfig and it work fine for all browsers.
Related
So, I have this issue with my emulators on Android Studio, sometimes they doesn't render the font
My emulators sometimes doesn't render the font, this happens with the keyboard, app names but it does not happen with the content of these.
I haven't found a solution other than delete the emulator and create a new one. I've tried different APIs and again it happens, it shows them well the first launches and then nothing.
Does anyone know why it happens or any way to repair them?
image1, image2, image3
This can sometimes be caused by the renderer / GPU having some sort of incompatibility.
Try changing your OpenGL ES renderer in the emulator settings. I've found "Desktop native OpenGL" to resolve the issue before.
Not directly a programming question but certainly one on developer productivity.
Like many developers I'm running the latest version of Firefox DeveloperEdition, to take advantage of all its various toolset, whilst trying to listen to Spotify to drown out the open plan office.
Whilst not the first time this has happened; Spotify crashes repeatedly with the WidevineCdm plugin being blamed as the culprit... this usually happens without any playback, but sometimes after a couple of seconds.
Usually "Help" page hints of fiddling with plugin settings as per usual aren't all that helpful.
I know that it'll likely resolve itself in a few days, but as a curious developer, I would like to know why it persistently breaks?
Unfortunately my fix to use Google chrome instead of Firefox :-(
This error just cropped up on Windows 7 ultra running Firefox to watch Netflix. (August 2019). Chrome worked OK as well as windows 10. For me i seemed to have found a solution (hopefully) After lots of digging and trying solution I have Netflix working OK by tuning Exploit Protection off in malware-bytes Premium .
I wanted to develop my own watchface for my Gear S2. I found some good documentation on downloading and using the Tizen IDE. All is well, but I'm finding the tweak css/html5-run/upload-switch faces-view-wash-rinse-repeat to be very tedious and time-consuming.
I know I can point my browser (Chrome) to my development workspace and load the index.html up and I surmise that I could tweak what I have, which came from the template to work in the browser if I made the sizes in the css static vs dynamic (absolute vs percentages). But is there a better way? Scouring the Internets Googles have yielded nothing too helpful yet.
moderators: this might be OT for this particular SO. If that's the case, I apologize. A nudge in the right direction would be greatly appreciated, if so.
So, I was able to make a little progress on this myself. I am using Chrome in developer mode, which almost works perfectly when using the developer device emulator. To toggle the device emulator, open developer mode (windows: ctrl+shift+I, OS X: cmd+option+i) and when the tool window opens up, look for the little device button next to the element button in the upper left corner of the developer tools window. When the device emulator open, switch the resolution to 320x320 (top of the window next to "screen").
Now, open your index.html file for your project in Chrome, and you can at least muck around with your css styling.
Now to get around the whole issue of reloading your clock with the default clock in the Java emulator for Tizen, I was able to get my changes to automatically assert when running the new code. The way I did it, though I'm not sure if all of these steps were necessary was:
In the emulated watch:
1. set the screen timeout to 15 mins.
2. set the watch face to your development watch face
In the IDE:
1. when ready, use the button for smart launch (it's the blue button just to the left of the bug button in the tizen web IDE). This is in the Tizen SDK version 2.3.1 build 20150721-1440.
At the time of running your code -- making sure both your emulated watch is running too:
1. In the IDE, click the smart launch button
2. Click over to your emulated watch and make sure it's in focus.
It should update the watch face with your latest changes in realtime. This worked for me, so YMMV, but at least I didn't have to reload the watch face after asserting the latest version.
I'm using Chrome 12 in a Linux 64bit box, but I can't get any of the samples bellow to work:
http://www.satine.org/research/webkit/snowleopard/snowstack.html
http://www.marcofolio.net/css/3d_animation_using_pure_css3.html
http://kevchapman.co.uk/css/webkit-css-perspective-demo/
They all use -webkit-perspective, but the final results differ a lot from the results got in Safari (Windows XP). So, after all, does Chrome support CSS 3D transforms? Or the support is still limited?
Thanks!
Go to the Chromium web SCM interface and check that your GPU isn't blacklisted.
Also, go to chrome://gpu/ and check that Chrome reports 3D CSS as enabled.
The problem is that 3d support in webkit browsers depends on your videocard. That's why you cannot see that examples, but your browser engine still supports 3d transforms. To resolve this problem you can use Modernizr, which detects browser+videocard 3dtranforms support.
I'm using Chrome on a Windows 7 machine right now, and all the demos seemed to behave exactly as they should have. Have you tried Chrome on your XP machine?
The company I work for is preparing for application testing in IE8. Previously we have been using IE6. Many of our web applications are written in .NET 1.0 and 1.1 with more recent apps written in 2.x and 3.x. I know IE8 has an IE7 compatibility mode and it says it has a quirks mode, but most of our apps were written for 6, which is not specifically mentioned. Compatibility is for 7, which had a compatibility for 6. I do not know if that is necessarily carried over to 8. In 6 quirks mode was to run 5.5 sites without a problem. With no deeper explanation on any of Microsoft's release notes does it mention quirks mode as 6 compliant or even 5.5, just a basis of what it is (specific DOCTYPEs or no DOCTYPEs).
If anyone could shed some light on how sites and apps designed for IE6 should run in IE8 would be greatly appreciated. If anyone else has made a similar move how smooth was the transition?
Thanks.
We made a similar switch in our company. We went from IE6 to IE8 across board, the only issues we noticed were related to styling. Now if you decide to upgrade your IIS server than that might cause some of your ASP apps to not work correctly.
The only thing you should notice is that you have ensured that your CSS will work correctly in IE8. You can install IE8 in your XP and see what will happen.
ASP.NET code is not important, Pay yout attation on HTML,CSS and JavaScript.
Quirks Mode has in principle not changed. IE8+ describes it as “IE5 document mode”. If your pages are still using Quirks Mode, then:
rendering should not change much;
oh dear. In 2010, really? That's sad.
IE is dragging along bugwards-compatibility for every version of IE since 5.5 except IE6. MS dropped IE6-standards-mode compatibility from IE7, then found the ensuing compatibility problems made it difficult to push people to upgrade to IE7 (and consequently depressed corporate sales of Vista). Since then they've made sure that each IE release has modes to simulate its predecessors, but it was too late to bring back IE6-standards-mode support.
This disastrous mess would never have happened if some idiot hadn't “integrated” the browser with the OS. If it weren't for that we could all just run the standalone IE versions we needed for the apps we needed.
And document rendering mode is only half the story. Getting the JavaScript to work consistently is often more of a problem, especially if the code was a dirty unreliable hack in the first place (which, in the case of webapps aimed at IE6, it often is). On the other hand, webapps that already worked on Firefox and other more standards-compliant browsers should work on IE8 with little to no change.