Skip to content

API changes/addition for asynchronous behaviour of new browsers #1406

Closed Answered by HeikoKlare
amartya4256 asked this question in Q&A

You must be logged in to vote

Thanks for your input. In general, I also like that pattern, but it puts an addition burden on clients, which should actually be unnecessary if the API was designed properly.

In today's dev community call, @akurtakov pointed to the WebKit implementation in SWT already dealing with the asynchronous API of WebKit. Looking at the implementation shows that it has the exact same challenge than Edge. Methods like setText and setUrl were solved by basically always returning true and delegating delegate asynchronous requests to WebKit, e.g.:

Replies: 1 comment 4 replies

You must be logged in to vote
4 replies
@laeubi

laeubi Aug 15, 2024
Collaborator

@sratz

sratz Aug 15, 2024
Collaborator

@laeubi

laeubi Aug 15, 2024
Collaborator

@HeikoKlare

Answer selected by amartya4256
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants