-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicated REQ_NEW_WINDOW from link #185
Comments
Is this related (?):
Some of the windows opened this way, seem to be unable to connect to uzbl-event-manager - at least there's just "[]" in the status bar where there should be "[Cmd]" instead.
|
Also claim ownership of temporary web view to avoid glib warning on exit Fixes uzbl#185
I don't think so. I have not seen that for a while. There is still a race condition (I think) when starting uzbl the first time when there is no event manager running |
I see both quite regularly:
|
I'm not really sure how to fix 1. I don't think there is a good way to check if we can actually connect to the socket without depending on something like socat for uzbl-browser I think the duplicate windows should be fixed by #186 if you have some small html snippet that demonstrate the other issues that would be great |
hello, the problem is relevant, when I open the link from the example, then a duplicate window opens. EVENT [1544] REQ_NEW_WINDOW 'http://google.com/' p.s. sorry, for my english |
the second event looks really odd. is it opening an empty window? if so this might be a new issue |
create #369 |
With a simple test page like
each time you click the link uzbl will send more and more REQ_NEW_WINDOW events. Starting from 1 and increasing by 1 each time so the 5th time you click the link 5 new windows are requested.
The text was updated successfully, but these errors were encountered: