commit | c1bac12f73e3e310018de943a36f7413b556035c | [log] [tgz] |
---|---|---|
author | Wenbo Jie <wenbojie@chromium.org> | Wed Nov 15 01:01:10 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 15 01:01:10 2023 |
tree | 519bf53796a38d75b1ef82b7c39139b9c0e41efa | |
parent | 3e2df989cf54598113c005155dc9c75995c8177b [diff] |
[FilesRefresh] Maintain the old initial loading behavior After the change in CL:5017845, Files app shows a blank screen in initial loading (before <xf-splitter> resolves), which is not consistent with what we have for FilesLegacy. This CL makes <xf-splitter> as a flex container before it resolves, so the slots (navigation list/header) can show earlier. Demo: (refresh Files 3 times) * no predefined style for xf-splitter(header in wrong position): http://go/scrcast/NjQyNjE1NTMzNzkwODIyNHwzY2YwMzA5OC0yMA * "display:none" before xf-splitter resolves(blank screen shows first): http://go/scrcast/NjY5ODE2OTEwNTY0NTU2OHxhN2M1MjMwNy0zOA * with this CL: http://go/scrcast/NDczMzExMDI2NzY3NDYyNHxhZmU4ZTA1ZC0yMQ Bug: b:301545020 Change-Id: Iba6e453e3f98de16832b16759202827ea7564b76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5028337 Reviewed-by: Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Wenbo Jie <wenbojie@chromium.org> Cr-Commit-Position: refs/heads/main@{#1224664}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.