maemo.org - Talk - Tear 0.3 - Simple WebKit browser, now with Dashboard

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - Tear 0.3 - Simple WebKit browser, now with Dashboard (https://talk.maemo.org/showthread.php?t=26475)

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by TrueJournals (Post 268431)

Typing about:blank into the address bar doesn't work for you?

it does, its just somewhat bothersome.

thanks tho, you made me think that it may be bookmarked ;)
(oops, should have checked first post earlier...)

btw, using the small osk seems to produce a good deal of double letters lately...

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

is there a way to make the menu open towards the center of the acreen? rot now it seems to allways drop down, and gets badly shrunk if it hts the lower edge...

ouch, creating a about:blank bookmark was a very bad idea!

1. it leads to a google search
2. dashboard now shows up empty

interesting, problem 1 goes away after restarting tear...

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

two new issues...

1. scrollbars in text areas do not stretch the full edge of a area...

2. while the options for scripts, plugins and images are shared between windows, at least the images setting is silently ignored by all other windows then the one where it was changed...

Re: Tear 0.3 - A WebKit-based browser, now with Dashboard

Quote:

Originally Posted by tso (Post 268455)

is there a way to make the menu open towards the center of the acreen? rot now it seems to allways drop down, and gets badly shrunk if it hts the lower edge...

I found the following comment in the r41242 webkit version of
WebKit/gtk/webkit/webkitwebview.cpp in the popup menu handler:

Code:

    // FIXME: The IntSize(0, -1) is a hack to get the hit-testing to result in the selected element.

    // Ideally we'd have the position of a context menu event be separate from its target node.

I'm looking into fooling it as-is (30 more minutes max :rolleyes:), but Bundyo could probably just patch webkit with most of his old placement code. This person probably punted because it's a little tricky if you're in a hurry. Let's face it, having scrolling, roving popup menus on a small screen is a high-class problem! Maybe Nokia has shared some of their tight-to-the-chest browser code in the latest SDK. :) But I bet there's something in the Android stuff. Anyway, I think these are the obvious main issues; their order is my best-guess as to their priority:

No menu item can be underneath the tap point
Neither the right or left edge can be off-screen because the menu only scrolls up and down
vertical_menu_exposure = vertical_menu_exposure_max with A and B still true
The menu's distance from the tap point is the minimum with A and B still true and C at max
And I think the menu has to grab the input focus, especially if the current tap point is not on the menu frame

And since things seem to be picking up, let's be optimistic and remove "Simple" from our comment titles. But knowing where I want to go with this I might have to start using clichés such as "Kitchen Sink" or "Swiss Army Knife" or "Left Nut."

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

just noticed that if i try to use any of the scroll arrows of that code area, the page takes of scrolling when i release screen pressure...

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Quote:

Originally Posted by tso (Post 268516)

just noticed that if i try to use any of the scroll arrows of that code area, the page takes of scrolling when i release screen pressure...

You don't like that feature? :) Yeah, seems as if the main_frame is handling child_frame button events. Makes sense; they're most likely being passed up. Damn, great catch.

@Bundyo, I think when scrolling you need to check the webview handlers for:

Code:

ev.window == wv.get_main_frame()

or maybe:

Code:

ev.window == wv.get_main_frame().window

Not really sure. They might be equivalent.

EDIT: No, the above is inaccurate. It only seems to have to do with auto_scrolling. Under non-auto_scrolling conditions (click-drag-pause/stop-release) everything seems fine.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

There's something wrong ...
You know the itt frontpage? Now look at these shots.. Different and wrong layout every time i call this page :confused:
There were no problems with 0.3-4

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

It makes me crazy. The problem disappeared after I made my last post with microb :D
(No, I don't think it has anything to do microb ;) )
I'll observe this ...

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

No, I've seen this before and couldn't reproduce it later. Not that I'm going much to the front page these days. :)

...On a side note, maybe one of the banners there is missing some closing tag or something. That can explain why it isn't always reproducible.

Re: Tear 0.3 - Simple WebKit browser, now with Dashboard

Love it! Look forward to the finished product with ad-blocker. Is there any way you can implement letting people organize their bookmarks in what ever order they want?