Fix: Term element in content value gets parsed #1414

lukewarlow · 2021-07-12T17:05:09Z

ai · 2021-07-12T17:17:17Z

lib/processor.js

@@ -497,6 +497,9 @@ class Processor {
        return true
      }
    }
+    if (node.type === 'decl' && node.prop === 'content') {


Suggested change

if (node.type === 'decl' && node.prop === 'content') {

if (node.prop === 'content') {

Only Declaration has prop.

ai · 2021-07-12T17:18:43Z

test/autoprefixer.test.ts

@@ -370,6 +381,9 @@ it('transition on vendor specific rule', () => {
 it('ignore prefix in vendor at rules', () => {
  check('at-rules')
 })
+it('ignore content property', () => {
+  check('content')


Suggested change

check('content')

let input = read('content')

let result = postcss([prefixer('scope')]).process(input)

expect(result.css).toEqual(input)

It will allow to avoid the same content in both files.

ai · 2021-07-12T17:30:52Z

Thanks. Released in 10.3.1.

Fix: Term element in content value gets parsed

9cc9b5e

ai reviewed Jul 12, 2021

View reviewed changes

Remove duplicate css and change check

923269e

ai merged commit 4e31573 into postcss:main Jul 12, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix: Term element in content value gets parsed #1414

Fix: Term element in content value gets parsed #1414

lukewarlow commented Jul 12, 2021

ai Jul 12, 2021

ai Jul 12, 2021

ai commented Jul 12, 2021

	if (node.type === 'decl' && node.prop === 'content') {
	if (node.prop === 'content') {

-  check('content')
+  let input = read('content')
+  let result = postcss([prefixer('scope')]).process(input)
+  expect(result.css).toEqual(input)

Fix: Term element in content value gets parsed #1414

Fix: Term element in content value gets parsed #1414

Conversation

lukewarlow commented Jul 12, 2021

ai Jul 12, 2021

Choose a reason for hiding this comment

ai Jul 12, 2021

Choose a reason for hiding this comment

ai commented Jul 12, 2021