This matches what I believe the OS native defaults to be.
Partially addresses #9487.
r? @metajack
cc @paulrouget
Source-Repo: https://github.com/servo/servo
Source-Revision: 180a9813aa5ecce0a3013cdd30c1ef99ed1d1f6d
I did this to see if it was a significant factor in automated test runs. (Spoiler: it isn't.)
Source-Repo: https://github.com/servo/servo
Source-Revision: 7b8bb0c2485eb46303d97918d91fce73bd98fea9
The default maximum line length Python linters use is 79, so a bunch of editor plugins complain about line lengths, unless you have a tox.ini telling the linter to ignore line lengths (E501) explicitly.
Source-Repo: https://github.com/servo/servo
Source-Revision: c3323f3c70ab53e5fe2f9aae7ba26b1a21cd622a
Gets rid of duplicate versions of bitflags and xml-rs!
Source-Repo: https://github.com/servo/servo
Source-Revision: e94f489e55e0fafed1c88b4d8f833f23545fc48b
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
Source-Repo: https://github.com/servo/servo
Source-Revision: f80641e7a16b832ce755cf936ed9ea6a9289fda9
Five of the BluetoothDevice members has been deleted in the spec:
8d148ba3c3
These were the vendorID, vendorIDSource, deviceClass, productID, productVersion.
Source-Repo: https://github.com/servo/servo
Source-Revision: a153e20c5503b6720d7abbfe36acfdda33a8d4dd
Stops the compiler complaining about `root_pipeline` being an unused variable.
Source-Repo: https://github.com/servo/servo
Source-Revision: 29ed65016047ee10dabf18894ba00ece6227e865
After actually reading a Python tutorial, I realised this can be handled
in a more elegant fashion :-)
Source-Repo: https://github.com/servo/servo
Source-Revision: 283eb4129664593f050e95c092e672a18f4658fc
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
Source-Repo: https://github.com/servo/servo
Source-Revision: bd871d613e9ed1ae4b7f1674275e69ba6da6133b
Build failed without it on my Ubuntu 14.04 machine. I can't confirm whether or not other OSes need it.
Source-Repo: https://github.com/servo/servo
Source-Revision: e52b9884d19b81dfc0e51986b1bbb89a227bfc4a
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.
Source-Repo: https://github.com/servo/servo
Source-Revision: ab12d8098fcc0517b64643d25683e2e15e665410
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).
Source-Repo: https://github.com/servo/servo
Source-Revision: a233d1e39b9549f7b24937ca4de9de0719bb890c
Patch by @fabricedesre from #11010, updated to fix test-tidy and to not conflict with other PRs in the queue. r? @larsbergstrom
Source-Repo: https://github.com/servo/servo
Source-Revision: 0baf665721c74b03c879a14f2fafc24a5dc6dda6
This uses the following bindgen commit:
64fe3d27be
r? @bholley
Source-Repo: https://github.com/servo/servo
Source-Revision: 95a1f7668cba3e903b2cee73caef121d286e9c3c
I mean, I like to convert seconds in my head, only almost every day ;)
Source-Repo: https://github.com/servo/servo
Source-Revision: fb5e00c2944533a4b365d26aadc41ca5b10cfefb
This is on top of #10999 so no need to review 8ae820b.
Source-Repo: https://github.com/servo/servo
Source-Revision: 319f520e4df2d1d904d57259b54bfa9e5e504f06
This helps with style struct alignment between Servo and Gecko.
Source-Repo: https://github.com/servo/servo
Source-Revision: 8bc4785bed662f87149260d87e030471c326ec88
I accidentally removed this code in #10936.
Fixes transitions.
r? @glennw
Source-Repo: https://github.com/servo/servo
Source-Revision: c1252a40d9925aea69346b1b2e35151f7fa397a4
This builds on top of #10815, so it's really just the last commit the one that should be reviewed.
I tried to apply the new infrastructure to servo, but failed (for now?).
The problem with it is that it'd require `ThreadSafeLayoutElement` to implement `selectors::Element`, which is a lot of work and might be racy (not totally sure about it though). Thus, I prefered to keep selectors eager until knowing that it's safe to do it.
r? @mbrubeck for style changes, @bholley for the geckolib changes (minimal for now, glue + a list of lazy PEs must be added)
Source-Repo: https://github.com/servo/servo
Source-Revision: 29823cb378ad0b05a82cfdd133c401a678a19007
Use `mem::replace` to perform the lifetime-trick without allocating a whole new buffer.
(An older of this switched from the built-in heapsort to a non-allocating introsort. Unfortunately, introsort is not a stable sorting algorithm, and the display list system relies on it being stable.)
Source-Repo: https://github.com/servo/servo
Source-Revision: 2e849b7064bdb30beedc4af13033b3f6a407f4b1
