Greetings,
For some personal reasons (increase education, increase personal control over web activity, decrease dependence on ‘foreign’ technology providers, and etc), I am making a new web browser using wxpython and html2.webkit/webview. The latter confusion is due to my working on Arch Linux on the OpenBox desktop
I’ve got a bit of experience working with python and similar, and between experience and the good work of the wxPython devs I have not required much in the way of help. With anything really Thanks for the great work
But, we all come to that point sooner or later.
I have the web browser based on the example html2 code, which is not an horrible bit of code as is; but I wanted better management of history, some light property inspection capability, bookmarking, and maybe a bit of application decoration support through graphic themeing so I have been modifying the code, albeit very slightly.
I encountered some inconsistencies, and thought ‘well now you’ve done it, barely touched these bits of code and now this’, but when I went back to the original example I find it does the same things, to wit:
some links will not open whjen clicked. I first noticed it happening on search results from startpage.com. Later, it was the articles at news.google.com (although google search return links behave as expected).
These unclickable links behave just as others do except they dont load when clicked: hover activity is proper, and copying the link usin g the context menu produces a pasteable link in the clipboard that looks and works fine when pasted into the browser’s combobox.
That whole bit ‘feels’ like an event is being trapped somehow and not making it as far down the event foodchain as it needs to go.
Additionally, I have embarked on providing some inspoection capabilty by binding some GetSource code to a KEY_DOWN sort of event, per the instructions.
This seems to work intermittently according to a pattern I’m only beginning to see take shape; it’s as if this will only retrieve the html source on pages who’s URLs have made it into the widget’s history.
The code is a complete app of course, is a bit awkward to post, but I’ll do so on request; I don’t feel it especially neccessary at present. I don’t have mysterious runtime errors or crashes, and the code works well with the exception of these fairly clear cases and no doubt some other similar cases I’ve yet to encounter. They generate no errors or warnings, they just don’t do all the things.
Might anyone have any insights?
Thanks in advance,
James