Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-11-10 02:01:03 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Userland/Libraries/LibWeb/Internals/Internals.idl

19 lines
464 B
Text
Raw Normal View History

LibWeb: Add an Internals API to trigger a user-activated (trusted) event Some DOM APIs are restricted to user-activated events. For example, you can't just invoke `navigator.clipboard.writeText` from JS - it has to be accompanied by a user gesture, such as a mouse-down event. This adds an Internals API to simulate such a gesture.
2023-11-10 16:19:37 -05:00
#import <DOM/EventTarget.idl>
LibWeb: Support committing changes to <input> elements We currently fire the change event on <input> elements when they lose focus. The spec allows for us to also fire the event when changes are "committed", so long as such an action makes sense for the input type. This patch detects when the return key is entered in an <input> element and uses that as the commit action for text-related types. If no change has occurred since the last commit, no change event is fired.
2023-11-30 12:54:30 -05:00
#import <HTML/HTMLElement.idl>
LibWeb: Add an Internals API to trigger a user-activated (trusted) event Some DOM APIs are restricted to user-activated events. For example, you can't just invoke `navigator.clipboard.writeText` from JS - it has to be accompanied by a user gesture, such as a mouse-down event. This adds an Internals API to simulate such a gesture.
2023-11-10 16:19:37 -05:00
LibWeb: Add a simple `internals` objects only available during testing This object is available as `window.internals` (or just `internals`) and is only accessible while running in "test mode". This first version only has one API: gc(), which triggers a garbage collection immediately. In the future, we can add more APIs here to help us test parts of the engine that are hard or impossible to reach via public web APIs.
2023-07-21 11:59:49 +02:00
[Exposed=Nobody] interface Internals {
LibWeb+WebContent+headless-browser: Support async text tests Previously, we used `on_load_finish` to determine when the text test was completed. This method did not allow testing of async functions because there was no way to indicate that the runner should wait for the async call to end. This change introduces a function in the `internals` object that is intended to be called when the text test execution is completed. The text test runner will now ignore `on_load_finish` which means a test will timeout if this new function is never called. `test(f)` function in `include.js` has been modified to automatically terminate a test once `load` event is fired on `window`. new `asyncTest(f)` function has been introduces. `f` receives function that will terminate a test as a first argument. Every test is expected to call either `test()` or `asyncTest()` to complete. If not, it will remain hanging until a timeout occurs.
2023-09-14 19:17:32 +02:00
undefined signalTextTestIsDone();
LibWeb: Add a simple `internals` objects only available during testing This object is available as `window.internals` (or just `internals`) and is only accessible while running in "test mode". This first version only has one API: gc(), which triggers a garbage collection immediately. In the future, we can add more APIs here to help us test parts of the engine that are hard or impossible to reach via public web APIs.
2023-07-21 11:59:49 +02:00
undefined gc();
LibWeb: Add hit testing API in `internals` object Introduces `internals.hitTest(x, y)` that is going to allow us write tests for hit testing :)
2023-08-08 22:44:52 +02:00
object hitTest(double x, double y);
LibWeb: Support committing changes to <input> elements We currently fire the change event on <input> elements when they lose focus. The spec allows for us to also fire the event when changes are "committed", so long as such an action makes sense for the input type. This patch detects when the return key is entered in an <input> element and uses that as the commit action for text-related types. If no change has occurred since the last commit, no change event is fired.
2023-11-30 12:54:30 -05:00
undefined sendText(HTMLElement target, DOMString text);
undefined commitText();
LibWeb: Run the unfocusing steps when a click does not focus anything For example, when clicking the document body outside of a focused input element, we should unfocus that element.
2023-12-03 09:54:26 -05:00
undefined click(double x, double y);
LibWeb: Add internals.wheel() to simulate mouse wheel events This function allows us to write tests for scrolling scenarios where the events are processed by the EventHandler.
2024-02-09 18:14:53 +01:00
undefined wheel(double x, double y, double deltaX, double deltaY);
LibWeb: Run the unfocusing steps when a click does not focus anything For example, when clicking the document body outside of a focused input element, we should unfocus that element.
2023-12-03 09:54:26 -05:00
LibWeb: Allow bypassing transient activation checks for tests We have a 5 second timeout between a user-activated event occurring and an activation-gated API being invoked in order for that API to succeed. This is quite fine in normal circumstances, but the machines used in CI often exceed that limit (we see upwards of 10 seconds passing between generating the user-activated event and the API call running). So instead of generating a user-activated event, add a hook to allow tests to bypass the very next activation check.
2024-02-20 16:30:26 -05:00
attribute boolean bypassNextTransientActivationTest;
LibWeb: Add a simple `internals` objects only available during testing This object is available as `window.internals` (or just `internals`) and is only accessible while running in "test mode". This first version only has one API: gc(), which triggers a garbage collection immediately. In the future, we can add more APIs here to help us test parts of the engine that are hard or impossible to reach via public web APIs.
2023-07-21 11:59:49 +02:00
};
Reference in a new issue Copy permalink