Community
Participate
Working Groups
If you run an application on the server, the app is executed on tomcat, and a browser is started. As far as I know on windows and linux the internal webtools html browser. On Mac OS X Safari does the job as external process. But Safari gets a wrong adress. For example Safari gets as html: file:///Users/reyez/Bibliothek/webDevelopment/eclipse/Eclipse.app/Contents/MacOS/http:/localhost: 8080/BrowserScanner .. should be of course http:/localhost:8080//BrowserScanner
no.. should be of course should be of course http://localhost:8080/BrowserScanner ..sorry..
1. There is an internal web browser for Mac OS X. I came from Linux where the internal web browser is the standard web browser viewing URLs. My wtp (M7) uses the external Safari as standard browser out of the box (General=>Web Browser). So you can easily switch the browser to "use internal browser" in the web browser setings and that's it. 2. I don't know why under Linux the internal browser is used as standard and on my Mac OS X machine Safari is the standard browser. (do you guys think that's consistent?). But thats no real bug. Just a little remark, and nothing to worry about. 3. If you deliver a default preference for Safari on Mac OS X in General=>Web Browser you should use the "open" command for opening Safari with an url instead of opening the core binary in the Safari package. The following settings work perfectly for me in General=>Web Browser => Edit. With that you only use one instance of Safari (The standard behaviour of all Mac Applications I ever saw), and you open the right URL. (no file://User/Whatever... is appended before the real URL). Name: Safari Location: /usr/bin/open Parameters: -a Safari %URL% hope that helps..
Tim, can you please comment?
This is an Eclipse browser bug, not WTP. It was already fixed several weeks ago and the fix is in recent WTP builds, so I'm going to just close this as fixed instead of passing to Eclipse and closing it/returning as a duplicate there.
This change is a bulk update of all _un_targeted, fixed, resolved bugs upon release of M5. This particular bug _might_ have been fixed earlier than M5. (Feel free to correct).
This is part of a mass update to close out all stale WTP resolved bugs from the 1.0.x and 1.5.0 timeframe. If you feel this bug was closed inappropriately, please reopen. Thanks, John Lanuti