I'm using IEtester to test in IE6, because the client want the page to be seen in it.
Till a few weeks ago, I could work as good as possible using the firebug lite Stable Channel in IE6 on the IETester. Now I can't! I don't know what changed... and I don't know how to work now, how to test the CSS online etc.
I have tried all the posibilities in http://getfirebug.com/firebuglite#Stable. Using the live link of each one, using the favorite button and/or downloading the firebug and adding a local link!
Nothing seems to work. Works only when I added this to the head of the page:
<script type='text/javascript' src='http://getfirebug.com/releases/lite/1.2/firebug-lite-compressed.js'></script>
But with that version I can't test the CSS live. I need to go to the CSS, write on the right column bla bla... thats the same as going to my own stylesheet page. That is not helping me...=(
I'm getting desperate with the IE6. Do you know a debugbug that I can use to test CSS live in a IE6 Tester?
If you had to work with IE6, how would you be working?
Please SOS me! =(
Thanks in advance.
You can try loading older versions of Firebug Lite, like this one which supports live editing of CSS rules:
https://getfirebug.com/releases/lite/1.3/firebug-lite.js
The best way to get support for problems in Firebug Lite is creating an issue report in our bug tracker:
http://code.google.com/p/fbug/issues/entry
Thanks!
There is only way to do this 100% correctly and that is running a real version of IE6. Get VirtualBox(Free) and install a Virtual Machine with XP running IE6.
Related
I recently started using the Dojo firebug extension. I had gotten used to it since it had some nice features (letting you see dojo on the widget level). This was good for me because I am in the process of trying to learn dojo so this really let me see how stuff worked together.
My question is, has anyone found any solutions to get the Dojo firebug extension working in Firefox 6 or should I just try downgrading to FF5?
Thanks
UPDATE:
I tried a workaround I found somewhere else. It said to use the Firefox nightly build add-on, and that add-on would allow me to override the version compatibility. I tried that and it still didn't work.
I recommend trying the Add-on Compatibility Reporter extension from Mozilla. This extension (besides letting you report incompatible add-ons) lets you completely disable version checking.
It's a great way to ensure that older extensions still work when Firefox upgrades the browser every week. Now, this assumes that the issue is with version compatibility, and not that the plugin is actually broken! If it's the latter, there's not much else you can do.
(Also, that's an awesome plugin. I'm definitely going to try it out myself here shortly!)
Background Info
I'm currently searching around for ways to add support for older versions of Internet Explorer for an existing project that uses Protovis (and therefore the tag). My searching around has led me to two main places:
http://multimedia.journalism.berkeley.edu/tutorials/protovis-internet-explorer/
Touches on the Chrome Frame plugin as well as SVGweb
https://gitorious.org/protovis/jloves-protovis
Seems to be an integration of Protovis with SVGweb
So far, I've downloaded the examples from each of these and opened them up in IE8 and have had no success whatsoever. The exact version of the IE is 8.0.7600.16385 and is running on a 64 bit Windows 7 Machine, and for the sake of SVGweb, the Flash version installed is 10.2.152.
The question(s)
Since I've had no luck making any of these work, I'm wondering if I'm doing something wrong. Can anyone verify that the examples found in http://multimedia.journalism.berkeley.edu/media/upload/tutorials/protovis/protovis-ie.zip and/or https://gitorious.org/~jlove/protovis/jloves-protovis/commits/master work in IE8? If not, is there any other way (preferrably server side, but if there is a plugin that users can download and install for IE8 that would be okay too) to make protovis work on older IE versions?
Thank you for any help or advice!
I never had any luck with either of those solutions either. However, datamarket.com have recently come up with a drop-in shim available from http://blog.datamarket.com/2011/06/22/protovis-support-internet-explorer-8/ which worked right out of the box for me. The only drawback is that interactive aspects of your visualisation may not work in IE using the shim - I had some drag-select functionality that I had to re-implement with sliders under IE.
Why processing.js is not running in IE8? For example the demo given in processing document http://processingjs.org/learning/topic/rollover
IE8 and before do not support <canvas> - no Internet Explorer before version 9 will work with Processing.js because of this.
I certainly agree with Mike regarding the limitations of IE8 and lower, but apparently it is still possible, though it doesn't work right out of the box. See related question "Has anyone got processing.js working in IE?"
im a bit new at extension development, but im about to embark upon a project to build a ffox extension.
Does anyone know if its possbile, with minimal adaption, to make a firefox extension compatible with ie8 as a plugin and if so, are there any caveats i should be aware of?
I guess its just javascript code wrapped around the ffox or ie8 wrapper, but would really appreciate to learn from someone who has experience.
Cheers
Ke
Others may know better than I but I don't think there's any "minimal adaptation" (<- I'm assuming you meant to say "adaptation") way to do this. IE plugins are COM and FF plugins are coded with JavaScript and XUL.
Please take a look at this code:
http://3wcloud-com-provisioning-qa.appspot.com/testAjaxDojo
Just tab off the "domain" input field to try to make the Ajax run.
(Note: the test Ajax web service always sends back the same message, it pretends to check if domain is available but it really doesn't).
When running in Firefox 3.5, I get "dojo not defined" on the dojo.xhrGet statement.
It works fine in IE7 and Chrome browsers, and one friend tested on Firefox 3.0 and it worked.
1) Is there something wrong with Firefox 3.5 not properly getting the dojo javascript from the CDN? Possibly a caching issue?
2) Do you Dojo gurus know of this problem? Is it something that has already been reported to Firefox?
Thanks,
Neal Walters
Update: 9/1/ afternoon - I have uninstalled and re-installed Firefox 3.5.2 (but I kept my profile settings), and got same problem. I'm on Windows Vista Ultimate.
Finally found the problem. It was the add-on called "No-Script". Even though I had set No-Script to allow scripts globally, something in that tool was causing the issue. I upgraded to new version of No-Script and still had problem. If I disable the add-on (from the Tools/Add-ons screen), then Dojo loads perfectly from the CDN and life is good again.
I probably lost 6-8 hours on this stupid issue. Hope this posts saves someone else the time. Please "vote-up" the answer if it does.
As I stated in my comment, on Firefox 3.5 (mac) works fine. Try to do the following on your Firefox browser, insert the dojo library url in the url bar:
http://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dojo/dojo.xd.js
Usually it helps to solve any cache problems and forces Firefox to fetch the file.
If it still doesn't work, just store dojo in your server and use it locally.
It's working fine here with NoScript enabled.
I just needed to allow both "3wcloud-com-provisioning-qa.appspot.com" and "ajax.googleapis.com".