aboutsummaryrefslogtreecommitdiffstats
path: root/components/script/dom/htmliframeelement.rs
Commit message (Collapse)AuthorAgeFilesLines
* Report use statements that use {} with only one entryCullen Rhodes2016-05-271-1/+1
|
* Record the frame type (IFrame or MozBrowserIFrame) in the pipeline.Alan Jeffrey2016-05-261-1/+3
|
* Move DOMString back to scriptAnthony Ramine2016-05-241-4/+5
| | | | This entirely removes the 'non-geckolib' feature of the util crate.
* Remove ConstellationChan.Ms2ger2016-05-191-11/+6
| | | | | | It's a pointless abstraction that propagates the obsolete chan terminology, swaps the order in which the sender and receiver are returned, and hides a source of panics.
* Removed unused importsPer Lundberg2016-05-151-1/+0
| | | | This fixes #11185.
* Stop using JSAutoRequest.Ms2ger2016-05-131-2/+1
|
* remove page and move functionality to browing contextConnor Brewster2016-05-111-6/+2
| | | | | | | | | | Allow for adding history items Fixed nested iframe test failure Cleanup and small refactors fixup
* Add and update some FIXME comments about origin handling with iframes.Ms2ger2016-05-021-0/+4
|
* Return a Url from HTMLIFrameElement::get_url.Ms2ger2016-05-021-13/+8
| | | | | Since Url::origin() always returns an opaque origin for about: urls, I don't believe this changes behaviour.
* Make IFrameLoadInfo take an Option<LoadData> instead of Option<Url>Keith Yeung2016-04-301-6/+7
|
* Auto merge of #10837 - asajeffrey:add-mozbrowsererror-details, r=Manishearthbors-servo2016-04-291-1/+9
|\ | | | | | | | | | | | | | | | | | | | | Add detail to mozbrowsererror events. Part of #10334. Once #10824 lands, we can include the panic reason and backtrace in the error report. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/10837) <!-- Reviewable:end -->
| * Add detail to mozbrowsererror events.Alan Jeffrey2016-04-251-1/+9
| |
* | Reduce channel cloning.Ms2ger2016-04-291-3/+3
| |
* | Avoid some clones.Ms2ger2016-04-291-1/+1
| |
* | script: Make iframes know their pipeline IDs at all times, even afterPatrick Walton2016-04-281-2/+8
|/ | | | | | | | | navigation. Since WebRender uses the pipeline ID stored in the iframe element to determine which pipeline to display, it had better be kept up to date! Closes #9919.
* Fix some compile warnings.Ms2ger2016-04-191-1/+1
|
* Use the document base url when resolving iframe URLsStephen (Ziyun) Li2016-04-151-2/+1
|
* Remove the url! plugin.Simon Sapin2016-04-141-1/+1
| | | | | | | | In rust-url 1.0 the `Url` struct is going to have private fields, and there is no way to to create an aribitrary one without going through the parser. The plugin never had a clear demonstrated performance benefit, it was made mostly because it was possible and relatively easy at the time.
* Remove containing_page_pipeline_idStephen (Ziyun) Li2016-04-141-10/+1
|
* replace Fallible<()> with ErrorResultDi Xu2016-04-131-5/+5
|
* Auto merge of #10399 - jdm:pb, r=jdmbors-servo2016-04-051-0/+13
|\ | | | | | | | | | | | | | | | | | | | | Private browsing - Initial steps Rebase of #10160. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/10399) <!-- Reviewable:end -->
| * Private browsing - Initial stepsdhaval06032016-04-041-0/+13
| |
* | No more headless compositor. Just the normal one.Michael Howell2016-03-241-1/+23
|/ | | | | | | | | This changes headless operation to strictly be a runtime option, rather than a compile-time one. Note that the old headless version still relied on a display server to support WebGL, while it now requires one all the time. Fixes #8573
* Add history information to mozbrowserlocationchange eventPaul Rouget2016-03-211-1/+9
|
* Auto merge of #9740 - paulrouget:mozbrowserconnected, r=jdmbors-servo2016-02-251-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | Support Browser API event mozbrowserconnected Fixes https://github.com/servo/servo/issues/9382 This new event is not yet documented. If this lands, I will add documentation to MDN. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.svg" height="40" alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9740) <!-- Reviewable:end -->
| * Support Browser API event mozbrowserconnectedPaul Rouget2016-02-241-1/+1
| |
* | allow mozbrowser only for top level windowsPaul Rouget2016-02-231-4/+11
|/
* Make iframes block the enclosing document's load event. Fixes #6663.Josh Matthews2016-02-101-2/+31
|
* Auto merge of #9244 - paulrouget:securitychange, r=jdmbors-servo2016-02-091-1/+19
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | mozbrowsersecuritychange event Fixes #8544 No test yet. Is there a way to mock a https connection? Also, I wish I could use the `HTTPSState` enum instead of a `String` when calling `trigger_mozbrowser_event` (https://github.com/servo/servo/compare/master...paulrouget:securitychange?expand=1#diff-30a18e04d7e0b66aafdf192e416cad44R306) but that would require `constellation_msg.rs` to know about `HTTPSState`, which is defined in `document.rs`, which would add a dependency to `components/msg`. I could define `HTTPSState` somewhere else maybe? Or maybe it's fine to use a `String`. But then, should I use the HTTPSState strings (`"modern/deprecated/none"`) or the mozbrowser strings (`"secure/insecure/broken"`) (as it is now) <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9244) <!-- Reviewable:end -->
| * mozbrowsersercuritychange eventPaul Rouget2016-02-091-1/+19
| |
* | Remove the global argument to EventTarget::{fire_event, fire_simple_event}.Ms2ger2016-02-081-2/+2
|/
* Make iframe's load event trigger a reflow of the enclosing window. Add a ↵Josh Matthews2016-01-261-1/+7
| | | | catch-all reflow for all same-origin pages sharing an event loop.a
* move MozBrowserEvent to script_traits (+ documentation)apopiak2016-01-131-3/+2
|
* moved IFrameLoadInfo and IFrameSandboxState to script_traitsFernando Martins2016-01-111-3/+4
|
* Auto merge of #8506 - nox:finish-ranges, r=dzbarskybors-servo2015-12-261-5/+3
|\ | | | | | | | | | | | | | | | | | | | | | | Properly propagate changes when range or trees are mutated Does the same thing as #6817, but storing Range instances directly in their start and end containers. Cc @dzbarsky <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8506) <!-- Reviewable:end -->
| * Introduce UnbindContextAnthony Ramine2015-12-131-5/+3
| | | | | | | | | | This holds the context that describes the original node that was removed from a tree when unbinding from a tree.
* | Auto merge of #9030 - askobara:refactoring-add-htmlformelement-fire_event, ↵bors-servo2015-12-221-7/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r=Manishearth Add helper method HTMLFormElement::fire_event Fixes #8777 <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9030) <!-- Reviewable:end -->
| * | Implement EventTarget::fire_simple_event and ↵Arthur Skobara2015-12-221-7/+3
| | | | | | | | | | | | EventTarget::fire_simple_event_params
* | | Precompute width & height attribute values on <iframe>Corey Farwell2015-12-221-6/+9
|/ /
* | Issue #8352: Dispatch mozbrowsershowmodalprompt event for alert().Simon Martin2015-12-191-1/+10
| |
* | Use Url.join instead of UrlParser.base_url(...).parse (#9002)Mathieu Agopian2015-12-181-3/+2
| |
* | Auto merge of #8618 - paulrouget:reload, r=jdmbors-servo2015-12-171-3/+8
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | Browser API: implement iframe.reload() fixes #8575 The implementation is naive, and doesn't support the `hardreload` parameter. And for the test, I'm not sure how else I can test the reload. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8618) <!-- Reviewable:end -->
| * Browser API: implement iframe.reload()Paul Rouget2015-12-081-3/+8
| |
* | Pass around event types as Atoms instead of StringsCorey Farwell2015-12-101-2/+2
| | | | | | | | | | | | `Event` internally stores the `type` as an `Atom`, and we're `String`s everywhere, which can cause unnecessary allocations to occur since they'll end up as `Atom`s anyways.
* | Move ScriptMsg from msg crate into script_traitsTomas Cernaj2015-12-091-1/+1
|/
* Auto merge of #8785 - mbrubeck:fixed-hit-test, r=pcwaltonbors-servo2015-12-041-0/+5
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add slow path for hit testing of iframe behind positioned content layer Fixes browser.html blocker #8759. r? @pcwalton This adds a slow path for cases where the compositor's layer-based hit testing is incorrect. If the script task discovers that a mouse event should have been dispatched to an iframe, it bounces the event back to the constellation to be forwarded to the correct pipeline. This isn't terribly slow (on the slow path, it adds one extra round-trip message between script and constellation), but if we want to optimize this better we could instead replace the compositor's layer hit testing with display list hit testing in the paint task. This would be a more complicated change that I think we should save for a follow-up. This only fixes mouse input for now. A basically-identical change will be needed for touch-screen input, whether we stick with this approach or switch to the paint task. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8785) <!-- Reviewable:end -->
| * If a mouse event is targeting an iframe, forward it to the iframe's inner windowMatt Brubeck2015-12-031-0/+5
| | | | | | | | | | | | | | | | Fixes #8759. This adds a slow path for cases where the compositor's layer-based hit testing is incorrect. To optimize for this case, we could instead replace the layer hit testing with display-list hit testing done in the paint task.
* | Remove unnecessary conversion to/from DOMString for localName.Eli Friedman2015-12-021-2/+2
|/
* Dispatch load events for cross origin iframes. Resolves #6672.Josh Matthews2015-11-301-1/+24
|
* Compute attribute name atoms at compile-time.Eli Friedman2015-11-271-2/+2
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-28 19:16:29 +0000