Hey i was wondering if anyone else has had problems with css 3d running on chrome on linux (specifically fedora 17). Chrome in Windows seems to handle everything fine but for some reason it won't work in Fedora. I get errors saying that my browser doesn't support 3d transforms.
Chrome/ium is probably the most popular option, so if the version you tried wasn't working, you may want to update to the very latest -- something like the Chromium Daily Builds. If even that is too buggy to work with, you might want to try a different Webkit browser for Linux.
Midori and Epiphany are two decent options. As an added bonus, I think both of these browsers will use the version of Webkit that you have installed on your system (unlike Chrome, which comes with its own version of Webkit). That means that you should be able to build Webkit from the latest nightly source release, and Midori or Epiphany will automatically use that version.
WebKit Nightly Builds
I hope that this help you.
Related
I was trying to make ObjectSpy work with Chrome browser but its unable to identify objects.
Whenever trying to identify getting this: WinObject("Chrome Legacy Window").
I tried reinstalling UFT and chrome and Microfocus extension for chrome but it didn't help.
I have downloaded extension from internet and its shows the version as Micro Focus UFT Agent
2022.0.1.25. My UFT version is 14.53. I am not sure if its compatibility issue.
Please help.
UFT 14.53 is pretty old as far as supported browsers are concerned (July 2019), if possible I would suggest upgrading to the latest version (upgrades are included in the license).
Failing that you can try to remove the extension from Chrome and install the one that comes with your version of UFT (in <UFT installation dir>/Installations) although I'm not sure it will work with current versions of Chrome.
I am using Google Chromium on Debian (the one in debian depository). I am hitting some bug, that crashes Chrome, but that I can replicate only in Chromium, not in Chrome. (It might be present in Chrome too, I just cannot replicate it.)
I can't figure out how to enable crash reporting in Chromium.
This guide doesn't work - I don't have that option in Advanced.
This guide describes:
Linux
Breakpad is compiled in, but is not enabled by default. See IsCrashReportingEnabled() in chrome_browser_main_linux.cc for details on when it is enabled.
Set the gyp variable (GYP_DEFINES) linux_dump_symbols=1 to dump the debugging symbols for the chrome binary in the Breakpad symbol format as part of a build.
chrome_browser_main_linux.cc does not have this function.
breakpad_linux.cc has a function IsCrashReporterEnabled, which is similar enough; however, I'm not too clever by staring at the code.
I am not sure what is gyp and if I have to use it. (I don't want to rebuild whole Chromium just to enable crash reporting.)
Enabling crash reporting on Chromium is not possible, since there are no official Chromium builds. Chromium is built by the distro maintainers (Debian, Red Hat) and it might or might not have the debug info.
The only builds Google does is Chrome from the Chrome website.
I'm looking for the way to conduct cross-browser compatibility test on my ubuntu. Firefox and opera don't cause problems, but I didn't find any guide how to install older versions of chrome. Do you know how to check my code in this browser on my computer?
You can take screenshots in different versions in Browserstack. Also you can browse there using different browsers, but you will need to pay for that.
In general, there is no need to test compatibility against anything but the latest version of Chrome, since Chrome updates itself automatically. Just expect that anyone using Chrome to view your site will have the latest version.
I bought a new Retina MacBook Pro to develop for iOS with MonoTouch.
It is extremely frustrating that, probably because it is built on Gtk#, MonoDevelop is very blurry.
I can cope with blurry UI but I can't read or write code because it hurts my eyes.
What is the current status of Retina support in Gtk# and MonoDevelop?
Is there any (experimental) compile flag at least to enable proper code rendering?
If I want to contribute, which component is in charge of this? Is it Gtk# or Gtk itself?
Update
This has been fixed as of MonoDevelop 3.0.4:
Other improvements and bug fixes
Fixed rendering on MacBook with retina display
So just go and download it.
Workaround for Older Versions (and other apps, too)
There is a temporary work around I used for WebStorm that worked well. It should work for MonoDevelop too.
You can use that in the mean time until the Xamarin folks get an update to MonoDevelop out.
Here it goes:
Locate MonoDevelop in Applications and click Show Package Contents
Open Contents/Info.plist in any editor and add this after opening <dict>:
<key>NSHighResolutionCapable</key>
<true/>
Copy and paste MonoDevelop app bundle, delete the old one and rename the new one back to MonoDevelop. This will flush system caches.
You will notice that MonoDevelop.app info now has Low Resolution option unchecked and the code renders smoothly.
I have some time now working with the BlackBerry's Eclipse Plugin with no issues using the Curve 8530 Simulator. Im trying to add the Torch 9800 Simulator but I get this:
Im pretty new on the BB Stuff.
Im I missing something?
Is there a debug-enabled version (I check and apparently the version that I have should be pretty capable of debugging)?
Help will be appreciated.
Edit: I noticed that I can only add simulators using OS v.5 (e.i BlackBerry Storm2 9550). But the why is still a mystery to me.
I've been looking for this issue for over a week, and the only think i can think of (yet not confirm) is that there are no debugging versions for OS other than 5x.
I was able to debug using all available models for OS5x (Pearl, Tour, Storm, Storm2, Bold, Curve)
So the official answer to this (until some one comes up with a more complete one) is...
There is no support for web debugging on versions other than OS 5x Simulators.
Not quite, I have a 4.6.0 simulator here (8220 "T-MobileEU" branded) that is debugging capable, but my 5.0.0 simulator (8530) is not listed as capable. The confusion continues.