Executing servo browser for the first time doesn't make evident that it already supports several different flags.
This patch implements a help message displaying the available options and a brief explanation on them, based on comments in source code (opts.rs).
I implemented both short hand/long hand options using getopts::groups.
function that has the application name (so in future, if the browser no longer
is named 'servo', the code will continue to work fine).
Signed-off-by: Adenilson Cavalcanti <a.cavalcanti@sisa.samsung.com>
This replaces flow construction with a strict bottom-up tree traversal,
allowing for parallelism. Each step of the traversal creates a flow or
a `ConstructionItem`, similar to how Gecko works. {ib} splits are
handled by not creating `InlineFlow`s until the containing block is
reached.
This should be able to be incrementalized by storing the `Flow` from
layout to layout, and performing fixups during flow construction
and/or wiping containing blocks in a previous pass.
r? @larsbergstrom
This replaces flow construction with a strict bottom-up tree traversal,
allowing for parallelism. Each step of the traversal creates a flow or
a `ConstructionItem`, similar to how Gecko works. {ib} splits are
handled by not creating `InlineFlow`s until the containing block is
reached.
This should be able to be incrementalized by storing the `Flow` from
layout to layout, and performing fixups during flow construction
and/or wiping containing blocks in a previous pass.
I was going to add the Constructor overload, but that requires implementing that fallthrough case in CGCase, which I didn't feel like doing. At least we can compile the dict now.
This isn't a full fix for #522 / #835 but it prevents the unrecoverable loss of work without changing the behavior of configure generally.
If configure drops committed local work, it can be recovered from the reflog.
This will fix#1201.
This maybe the work in progress.
@jdm:
* Should we pass `DOMString` directly to `dom::utils::null_str_as_...`?
* Do you have any good idea to update the comment in `CodegenRust.py`?
This isn't a full fix for #522 / #835 but it prevents the unrecoverable
loss of work without changing the behavior of configure generally.
If configure drops committed local work, it can be recovered from the reflog.
