cdb07dc94f
Three review points on the border removal. The width half of "the size it was" read `style.minWidth` back, which is the same string whether or not the box it produces is right -- a content-box regression would have passed it. The bar is now mounted in a 40px wrapper so the min-width floor is exercised by layout and `getBoundingClientRect` measures it; reverting to 5rem fails all four themes. "`--head` is off both surfaces in every theme" overstated the monochrome case: amber is 1.11 against a Panel and 1.04 against the page, night 1.05 and 1.01. Amber can afford a brighter track and now takes `--table-line` (1.34 / 1.43). Night cannot -- the label crosses the empty track and measures 5.25 at `--head`, 4.22 at `--table-line`, 3.42 at `--border`, so every track with a visible edge puts the label under 4.5. That is recorded as a deliberate near-flat track rather than described as an edge it does not have. And the single `> 1.05` floor had no slack in night, where the real ratio is 1.053, so it asserted "not the same color" while reading like a visibility claim. Each theme is now held to its own measured floor, against the page as well as the Panel -- bars land on both -- with night's 1.04 / 1.005 naming what that theme really does. |
||
|---|---|---|
| .. | ||
| cypress | ||
| public | ||
| scripts | ||
| src | ||
| .gitignore | ||
| cypress.config.js | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| serve.json | ||
| tsconfig.json | ||
Getting Started with Create React App
This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more
information.
npm run build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will
remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right
into your project so you have full control over them. All of the commands except eject will still work, but they will
point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you
shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't
customize it when you are ready for it.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
Code Splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
Analyzing the Bundle Size
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
Making a Progressive Web App
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
Advanced Configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
Deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
npm run build fails to minify
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify