Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Merge requests
  • !35474

[WIP]: using fallback values insteead of explicit declarations

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Administrator requested to merge fod-css-vars-tooltip into main Dec 07, 2021
  • Overview 1
  • Commits 9
  • Pipelines 0
  • Changes 8

Created by: ffoodd

Only a POC to check if using fallback values instead of explicit custom properties declarations could save bytes.

The rationale to switch to fallback values or not is the number of occurrences: (, + value) × n occurrences should be longer than the whole explicit declaration. I did not count it for now but that should IMHO be the decision tree.

The only exception would be font-sizes since RFS could behave differently depending on the value. Using its output as a fallback isn't safe.

Let's check Bundlewatch, now :D

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fod-css-vars-tooltip