You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previous beta b.1 would choke if <style> element was added to the <head> section in a html file.
The latest beta b.2 accepts <style> element in the <head> but still chokes if one adds any CSS selector there.
Environment
OS: Mac
Package Manager: bun -1.1.28
JS Runtime: bun
Minimal Reproduction
Create an index.html page in a folder (allowed as per the documentation ) add <style> element to the <head> element with any CSS rule in it. You will get the error below.
If <style> element is empty there is no error. It seems the parser chokes on ";".
The documentation states that:
You can go extreme and override the entire html element in which case you can customize everything inside the html element, including the document head.
If the <style> element is not allowed in the <head> element for some reason then we should update the documentation.
The text was updated successfully, but these errors were encountered:
Describe the Bug
Previous beta b.1 would choke if <style> element was added to the <head> section in a html file.
The latest beta b.2 accepts <style> element in the <head> but still chokes if one adds any CSS selector there.
Environment
Minimal Reproduction
Create an index.html page in a folder (allowed as per the documentation ) add <style> element to the <head> element with any CSS rule in it. You will get the error below.
If <style> element is empty there is no error. It seems the parser chokes on ";".
Logs & Additional Context
I get the following error:
{
title: "Rendering error",
expr: "\n h1 {\n color: orange;\n }\n ",
subexpr: ";",
text: "SyntaxError: Unexpected token",
line: 25,
}
The documentation states that:
You can go extreme and override the entire html element in which case you can customize everything inside the html element, including the document head.
If the <style> element is not allowed in the <head> element for some reason then we should update the documentation.
The text was updated successfully, but these errors were encountered: