aboutsummaryrefslogtreecommitdiffstats
path: root/vanilla/node_modules/css-tree/lib/syntax/node/Ratio.js
diff options
context:
space:
mode:
authorAdam Mathes <adam@adammathes.com>2026-02-14 14:46:37 -0800
committerAdam Mathes <adam@adammathes.com>2026-02-14 14:46:37 -0800
commitafa87af01c79a9baa539f2992d32154d2a4739bd (patch)
tree92c7416db734270a2fee1d72ee9cc119379ff8e1 /vanilla/node_modules/css-tree/lib/syntax/node/Ratio.js
parent3b927e84d200402281f68181cd4253bc77e5528d (diff)
downloadneko-afa87af01c79a9baa539f2992d32154d2a4739bd.tar.gz
neko-afa87af01c79a9baa539f2992d32154d2a4739bd.tar.bz2
neko-afa87af01c79a9baa539f2992d32154d2a4739bd.zip
task: delete vanilla js prototype\n\n- Removed vanilla/ directory and web/dist/vanilla directory\n- Updated Makefile, Dockerfile, and CI workflow to remove vanilla references\n- Cleaned up web/web.go to remove vanilla embed and routes\n- Verified build and tests pass\n\nCloses NK-2tcnmq
Diffstat (limited to 'vanilla/node_modules/css-tree/lib/syntax/node/Ratio.js')
-rw-r--r--vanilla/node_modules/css-tree/lib/syntax/node/Ratio.js68
1 files changed, 0 insertions, 68 deletions
diff --git a/vanilla/node_modules/css-tree/lib/syntax/node/Ratio.js b/vanilla/node_modules/css-tree/lib/syntax/node/Ratio.js
deleted file mode 100644
index c26cf10..0000000
--- a/vanilla/node_modules/css-tree/lib/syntax/node/Ratio.js
+++ /dev/null
@@ -1,68 +0,0 @@
-import {
- Delim,
- Number as NumberToken,
- Function as FunctionToken
-} from '../../tokenizer/index.js';
-
-const SOLIDUS = 0x002F; // U+002F SOLIDUS (/)
-
-// Media Queries Level 3 defines terms of <ratio> as a positive (not zero or negative)
-// integers (see https://drafts.csswg.org/mediaqueries-3/#values)
-// However, Media Queries Level 4 removes any definition of values
-// (see https://drafts.csswg.org/mediaqueries-4/#values) and refers to
-// CSS Values and Units for detail. In CSS Values and Units Level 4 a <ratio>
-// definition was added (see https://drafts.csswg.org/css-values-4/#ratios) which
-// defines ratio as "<number [0,∞]> [ / <number [0,∞]> ]?" and based on it
-// any constrains on terms were removed. Parser also doesn't test numbers
-// in any way to make possible for linting and fixing them by the tools using CSSTree.
-// An additional syntax examination may be applied by a lexer.
-function consumeTerm() {
- this.skipSC();
-
- switch (this.tokenType) {
- case NumberToken:
- return this.Number();
-
- case FunctionToken:
- return this.Function(this.readSequence, this.scope.Value);
-
- default:
- this.error('Number of function is expected');
- }
-}
-
-export const name = 'Ratio';
-export const structure = {
- left: ['Number', 'Function'],
- right: ['Number', 'Function', null]
-};
-
-// <number [0,∞]> [ / <number [0,∞]> ]?
-export function parse() {
- const start = this.tokenStart;
- const left = consumeTerm.call(this);
- let right = null;
-
- this.skipSC();
- if (this.isDelim(SOLIDUS)) {
- this.eatDelim(SOLIDUS);
- right = consumeTerm.call(this);
- }
-
- return {
- type: 'Ratio',
- loc: this.getLocation(start, this.tokenStart),
- left,
- right
- };
-}
-
-export function generate(node) {
- this.node(node.left);
- this.token(Delim, '/');
- if (node.right) {
- this.node(node.right);
- } else {
- this.node(NumberToken, 1);
- }
-}