MiniBrowser with haikuwebkit2; with working keyboard, scrolling and mouse
(The ticket updates tab was hovered with the mouse)
Thanks also to @Zardshard @PulkoMandy and @madmax for their other work on webkit, and help with webkit2 So I could focus on this… 
Now, some issues are still to iron out, like crashes, some redraw, and focus issues. But I’m quickly noting all of those down on the bugtracker.
If codeberg approves my request for a repository I can soon(ish) upload the patches.
Nice work! Well done to the full team 
Oh, nice! Looks like MiniBrowser is now (once you get the changes uploaded) getting pretty usable!
Of course, there is still probably a lot of work left to integrate WebKit2 with WebPositive, but we’re getting there
Yeah. 
My plan is to make a “new” WebPositive, marry that with webkit2 and gradually move over code and rework it, developing the functionality webkit2 needs in tandem.
by beta6 that will either be finished, or we’ll have a demo. We’ll see.
I think from you specifically I could use some help for these two tickets, if you have time anyhow
Oh, nice plan! That way you always have something that works nicely and you can build out slowly instead of having to always see what features still need to be integrated before WebPositive with WebKit2 reaches feature-parity with WebPositive with WebKitLegacy.
Ah, I didn’t know we used Trac for WebKit. Now if only I could subscribe to the webkit2 keyword or the “Kits/Web Kit” component. @PulkoMandy (IIRC) set me as the owner of all new Icon-O-Matic tickets so I get notified for those, but setting me as the owner of webkit2 tickets obviously likely isn’t going to be a good idea.
I may have an idea of what is wrong, but my WebKit build is out of date so time to wait all day for that to build! 
I can simply add you to the CC for all tickets i tag webkit2, if you care for that?
I can make you the default owner of the Web Kit component if you want. I don’t mind not receiving the notifications, since I watch the bugtracker manally regularly anyways.
Hmm, that would be a bit strange but it would get the job done. I guess my preferred option is having nephele CC me for their WebKit2 tickets.
You can get an RSS from a query. For example: webkit2 keyword. You’d still have to open the ones you are really interested in and CC yourself if you also want a mail for every change, though.
Nice, that works for me! No more need to CC me @nephele
That looks very nice and also promising regarding further news. <3
congratulations!
What’s the status as of today? Is the bugtracker list up-to-date? (Keyboard input is working according to this topic but the ticket is still open.)
I am interested in contributing to this effort.
Hi KapiX,
The bugtracker is up-to-date.
My patches are in this ticket: Making sure you're not a bot!
I am having some troubles upstreaming since I do not have a github account. The codeberg issue to increase our storage limit so we could migrate (or have a mirror there) seems a bit stalled since codeberg has not finished their storage quota stuff.
Codeberg issue: #866 - Raise Haiku's storage limit (i.e. for a Webkit repository) - Codeberg-e.V./requests - Codeberg.org
Status in the haiku-webkit2 branch as far as I know: I keep it rebased but I do only minimal testing. Keyboard and mouse are working but mouse wheel is not. Rendering is flickering a lot. Mousewheel does not work. Some classes are missing because the only available implementations in webkit require egl. Simple websites will work, but anything needing these display/rendering classes will hit a null pointer or assert. That includes Google landing page, for example.
I implemented keyboard and mousewheel in the same patch series, so that is interesting, it seems the keyboard patch is not in the branch if i see this correctly though.
edit: one patch for the keyboard is in the main branch already though to move some things into a utility class shared between both
Hey @KapiX,
I see you uploaded the patches, neat!
Just a fyi that I can’t review the PR at all because I can’t view it. Github rate limits me on the uhm, first request to view the PR 
I have compiled successfully webkit2 from the GitHub - haiku/haikuwebkit: Official Haiku fork of the WebKit repository repo (branch haiku-webkit2), but when launching minibrowser I have the below error.
Is there anything I have missed?
The script seems to be misconfigured/broken. But you can start MiniBrowser directly by running its executable in WebKitBuild/Release/bin/MiniBrowser
