- This topic has 8 replies, 5 voices, and was last updated 18 years, 6 months ago by
Riyad Kalla.
-
AuthorPosts
-
sbarlowMemberUsing Eclipse 3.1.0, ME 4.1.0 GA on win 2000 (sp4)
I’m trying to debug javascript in a webapplication which controls access based on the connecting browser. At the moment, it will only allow Internet Explorer user agents to connect.
I altered the setting in Window->Preferences->MyEclipse->Internet Tools to “Internet Explorer”, restarted Eclipse and recreated a debug javascript application entry but when I kick-off a debug session, it insists on using the built in Web2.0 brower.
Know what’s going wrong?
Another solution would be to somehow modify the user-agent string used by Web2.0 browser to appear to be an IE browser. Is this somehow possible? Any help appreciated.
Thanks!
Stuart.
January 27, 2006 at 9:27 am #245512
GregMemberStuart,
The Web 2.0 browser uses Gecko rendering internally so the user agent will be mozilla based. There is no way to substitute in IE inside the web20 browser. An interesting idea would be to allow different user agents, sorta like Opera does. I will send that idea up to management.
January 27, 2006 at 10:35 am #245525
Riyad KallaMemberStuart,
The Web 2.0 browser is specially instrumented to hook into the debugger, you can’t switch it out with other browsers at this time.February 10, 2006 at 7:22 am #246511
harryajhMemberUsing Eclipse 3.1.0, ME 4.1.0.GA on win 2000 (sp4)
We have a similar problem, our intranet app is targeted at IE 5.5 (sp2) & no other browser (the client wants us to make us of IE’s API!) – strange but true!
When debugging javascript the browser opened looks like Firefox (not surprising reading a reply above regarding Gecko!)!
Some sections of the app are password controlled & we use IE’s window.showModalDialog() function instead the standard prompt() so passwords entered aren’t visible – this obviously doesn’t work in FF so are we stuffed then?
We could add code to get around this which obviously takes extra time but it looks like we can’t use Javascript debugging then?
Is this likely to change in future versions?
many thanks
harry
February 10, 2006 at 8:00 am #246515
Riyad KallaMemberharry,
Yes this will likely change in the future, but not right away (say in 5.0).February 10, 2006 at 10:13 am #246525
harryajhMembercan you give me any idea when 5 is due? (makes a big difference to what we do now!)
February 10, 2006 at 10:40 am #246528
Riyad KallaMember5.0 Milestone 1 we are hoping to have out around EclipseCon, then we are shooting for the final release inline with Eclipse 3.2 at the end of June.
December 5, 2006 at 5:19 am #263031
Nicole WilmsMemberAny news about using Internet Explorer with the Web2.0 javascript debugging?
Edwin
December 5, 2006 at 9:29 am #263039
Riyad KallaMemberEdwin,
There are no plans to support the JS debugging on IE, the reason is the underlying framework APIs that allow us to call into the dom and do debugging correctly. -
AuthorPosts