Bug 223158 - Browser support - Safari - javascript:open strange results
Summary: Browser support - Safari - javascript:open strange results
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.3.2   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal with 5 votes (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 324244 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-03-18 23:21 EDT by David Sugar CLA
Modified: 2019-09-06 16:12 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Sugar CLA 2008-03-18 23:21:13 EDT 
I'm working on a creating a standalone application with Eclipse.  As part of this application there is an embedded web browser.  I am creating a new 'Browser' object.  The style is 'SWT.NONE', so it is creating the embedded Safari browser as this is a Mac.

As part of this browser, there is some javascript calling window.open and I'm passing in specific values for the width and the height of the window to be created.  But when the sizes get into eclipse they have changed.

I have traced to the java org.eclipse.swt.browser.Safari  - function setFrame (around line 1007).  It seems the memmove is not correct.  I'm guessing that something changed in Safari to break this because I know that it worked at one point - not to terribly long ago and I don't think I had updated eclipse from when it was working to when it broke.  I just updated Eclipse to the latest tonight and it is still broken.

I have Safari version 3.0.4 (523.12.2) installed.  

I'm not sure where this value is coming from for how to debug closer to the source.
Comment 1 Grant Gayed CLA 2010-09-15 12:51:38 EDT 
*** Bug 324244 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:12:38 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.