Hi Humdinger, Von: "Humdinger" <humdingerb@xxxxxxxxxxxxxx> > Hi. (Not sure I'm even allowed to reply to a webkit-commit message...) Sure!! > -- webkit@xxxxxxxxxxxxxxx, on Fri, 02 Apr 2010 21:19:29 +0000: > > * Make sure in the closeWindowSoon() hook that JS code cannot find > > the page > > anymore. (As in Chromium port.) > > * Do not ignore createWindow() requests when the resource request is > > empty. > > Follow the Chromium port and always create a window object, start > > loading > > when the request is not empty. This allows the translation page of > > the > > Haiku guide translatoin site to function. > > Now the user guide translation site > http://userguide.haikuzone.net/documents.php > does open a translation panel in a new tab. BTW, in Bezilla - although > set to open new pages in new tabs - this panel opens in a new window. > This is intended behaviour, allowing you to see the entire page in the > background. > Can Web+ be tweaked to accept this special case, too? I have no idea > how the translation panel is acually called. Maybe Vincent can help. Ok, it is possible for WebPositive to open new pages in tabs or new windows, that's not a technical constraint. I just hate it usually when new pages are opened in new windows. Which makes this a problem of how to differentiate this particular case, but I am confident it's possible somehow. > More serious: closing this panel-in-a-tab will quit Web+ completely! No > Terminal output. Ok, that one will be interesting. I never bothered to close the tab when testing... thanks for the report! Best regards, -Stephan