use onload in iframe test
the iframe test is implemented using setTimeout function
Since the iframe already implement load event, replacing
timeout function with load event.
<!-- 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/11053)
<!-- Reviewable:end -->
Remove redundant code in whitespace stripping
LineBreaker calls Fragment::strip_trailing_whitespace_if_necessary and then recalculates the fragment's inline size. But this isn't necessary because strip_trailing_whitespace_if_necessary already recalculates the size.
r? @pcwalton
<!-- 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/11039)
<!-- Reviewable:end -->
Remove BluetoothDevice members
Five of the BluetoothDevice members has been deleted in the spec:
8d148ba3c3
These were the vendorID, vendorIDSource, deviceClass, productID, productVersion.
<!-- 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/11028)
<!-- Reviewable:end -->
mach run --debug: Use nicer syntax in rust-gdb/rust-lldb check
After actually reading a Python tutorial, I realised this can be handled
in a more elegant fashion :-)
<!-- 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/11013)
<!-- Reviewable:end -->
Don't let restyle damage infect siblings
Currently `compute_layout_damage` does the following for each child of the node it's processing.
1. Update the child with damage from the parent.
2. Update the parent with damage from the child.
When these steps are repeated for the next child, the parent's damage may include flags that came from its previous sibling(s). This means that damage ends up propagating to later siblings, and not just between parents and children as indended.
This patch propagates the same damage to all children, not including any damage from their siblings.
r? @pcwalton
<!-- 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/11037)
<!-- Reviewable:end -->
Add dbus to list of Debian build deps
Build failed without it on my Ubuntu 14.04 machine. I can't confirm whether or not other OSes need it.
<!-- 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/11040)
<!-- Reviewable:end -->
Set max log level on all platforms
Servo currently enabled the `release_max_level_info` feature for the log crate
in an Android-specific dependency. Currently this works for all platforms
because of rust-lang/cargo#2524, but it might break if that issue is fixed.
<!-- 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/11033)
<!-- Reviewable:end -->
LineBreaker calls Fragment::strip_trailing_whitespace_if_necessary and then
recalculates the fragment's inline size. But this isn't necessary because
strip_trailing_whitespace_if_necessary already recalculates the size.
Currently `compute_layout_damage` does the following for each child of the
node it's processing.
1. Update the child with damage from the parent.
2. Update the parent with damage from the child.
When these steps are repeated for the next child, the parent's damage may
include flags that came from its previous sibling(s). This means that damage
ends up propagating to later siblings, and not just between parents and
children as indended.
This patch propagates the same damage to all children, not including any
damage from their siblings.
Use NEON build flag on ARM and AArch64
The NEON flag is already used when building for Android, this patch enables it on other ARM devices too.
Note that this patch just adds the build flag to the compilation, for actually enabling the SIMD code in Servo, we'll also need #10900 (but it's not a dependency).
<!-- 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/10916)
<!-- Reviewable:end -->
Servo currently enabled the `release_max_level_info` feature for the log crate
in an Android-specific dependency. Currently this works for all platforms
because of rust-lang/cargo#2524, but it might break if that issue is fixed.
Update to Rust nightly 2016-04-29
Patch by @fabricedesre from #11010, updated to fix test-tidy and to not conflict with other PRs in the queue. r? @larsbergstrom
<!-- 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/11017)
<!-- Reviewable:end -->
