Results (11 - 20 of 95)
- [266656]: CSS :visited color taken on non-visited link when using CSS variables ...
- CSS :visited color taken on non-visited link when using CSS variables https://bugs.webkit.org/show_bug.cgi?id=210525 Source/WebCore: Patch by Tyler Wilcock <twilco.o@protonmail.com> on 2020-09-04 Reviewed by Darin Adler. This patch fixes a bug in which :visited styles with variables (custom p ...
- By Sep 4, 2020 11:43:37 PM —
- [262627]: CSS Variables: Color on specific `border` properties does not work. ...
- CSS Variables: Color on specific `border` properties does not work. https://bugs.webkit.org/show_bug.cgi?id=211672 Patch by Tyler Wilcock <twilco.o@protonmail.com> on 2020-06-05 Reviewed by Antti Koivisto. Source/WebCore: Properly mark C ...
- By Jun 5, 2020 10:22:07 AM —
- [259929]: Web Inspector: CSS: variables should have a go-to arrow to quickly ...
- ... Often when debugging/editing styles that use CSS variables, the desired workflow is to modify the variable itself, not that specific usage. This is especially helpful when editing colors saved in CSS variables. Add an always visible go-to arrow immediately after the variable (e.g. `- ...
- By Apr 11, 2020 8:14:34 AM —
- [252167]: Support CSS Dark Mode for PrettyDiff.rb. ...
- ... rb: Modify CSS to support dark mode. I used CSS variables in places where colors were shared, but otherwise provided alternate style rules individually. Some colors looked fine in both appearances, and those I left with only their light definition.
- By Nov 6, 2019 6:42:48 PM —
- [251919]: Web Inspector: Settings: Blackbox: hide icon is missing ...
- ... d of that specific part won't be included, meaning that any CSS variables used for controlling colors won't exist. Adding a fallback value to the `var()` for these cases allows a specific part to be used without needing any surrounding styles. * UserInterface/Views/BlackboxSettingsView.css: (.setti ...
- By Nov 1, 2019 8:53:02 AM —
- [251883]: Web Inspector: REGRESSION(r251038): Elements: Computed: variables are ...
- ... tyleSection` so that the Computed details panel can prevent CSS variables from being shown in the Properites section. * UserInterface/Views/SpreadsheetCSSStyleDeclarationSection.js: (WI.SpreadsheetCSSStyleDeclarationSection.prototype.get propertiesToRender): Replace `variable` getter with `isVariab ...
- By Oct 31, 2019 3:00:22 PM —
- [248940]: Web Inspector: Sources: increase the filter bar's width when it's ...
- ... (@media (prefers-color-scheme: dark) :root): Expose some CSS variables in light mode that were previously only defined in dark mode. * UserInterface/Views/NetworkTableContentView.js: (WI.NetworkTableContentView.prototype._updateFilteredEntries): (WI.NetworkTableContentView.prototype._updateURLFi ...
- By Aug 21, 2019 3:30:57 AM —
- [248916]: Web Inspector: Sources: move the resource type scope bar to be next to ...
- ... selected):hover::after): Added. Introduce CSS variables for `margin`, `padding`, and `opacity` that callers can override to customize the appearance of the `WI.ScopeBar`. * Localizations/en.lproj/localizedStrings.js:
- By Aug 20, 2019 2:11:11 PM —
- [248480]: Web Inspector: Sources: increase the vertical space allocated to the ...
- ... details-section): (.details-section > .header): Create CSS variables for styles that will be overridden by the Sources navigation sidebar.
- By Aug 9, 2019 2:59:29 PM —
- [247179]: Web Inspector: current call frame indicator not visible in dark mode ...
- ... call-frame.selected .status > .status-image): Replace the CSS variables used for `fill` with their actual color value (in `light` mode), as the semantic "name" of the variable doesn't really match its usage. As an example, the current call frame shouldn't rely on the value of `--border-color`, as ...
- By Jul 5, 2019 2:48:54 PM —
Note: See TracSearch
for help on searching.