[Docs] fixes
Stylistic and other fixes R=andybons@chromium.org BUG=524256 Review URL: https://codereview.chromium.org/1318153003 Cr-Commit-Position: refs/heads/master@{#346569}
This commit is contained in:
docs
how_to_extend_layout_test_framework.mdlinux_build_instructions.mdlinux_build_instructions_prerequisites.mdlinux_cert_management.mdlinux_chromium_arm.mdlinux_debugging.mdlinux_debugging_gtk.mdlinux_debugging_ssl.mdlinux_development.mdlinux_eclipse_dev.mdlinux_faster_builds.mdlinux_graphics_pipeline.mdlinux_gtk_theme_integration.mdlinux_hw_video_decode.md
@ -106,7 +106,7 @@ I actually tried this locally. There's a sort of uncanny valley effect going on;
|
||||
as the frame looks more native, it's more obvious that it isn't behaving like a
|
||||
native frame. (Also my implementation added a startup time hit.)
|
||||
|
||||
### Why use style properties instead of (i.e.) `bg[STATE]`?
|
||||
### Why use style properties instead of (i.e.) bg[STATE]?
|
||||
|
||||
There's no way to distinguish between colors set on different classes. Using
|
||||
style properties allows us to be backwards compatible and maintain the
|
||||
|
Reference in New Issue
Block a user