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
Responsive CSS should be able to target elements using classes.
Actual behavior.
Because styles are being inlined, classes are being removed from elements which causes responsive CSS code to no longer work.
Steps to reproduce the problem.
Use the following code in the editor. In my case the code changes after the code is rendered.
The following code is what I enter into the editor.
<!DOCTYPE html>
<html>
<head>
<style>
.main {
background:green
}
@media only screen and (max-width: 657px) {
.main { background:red }
}
</style>
</head>
<body>
<div class="main">
Oh hai mark
</div>
</body>
</html>
Then it's rendered as this:
<!DOCTYPE html><html><head><style>
.main {
background:green
}
@media only screen and (max-width: 657px) {
.main { background:red }
}
</style></head><body aria-disabled="false">
<div fr-original-style="" fr-original-class="main" style="background: green;">
Oh hai mark
</div>
</body></html>
Editor version.
I don't know it. I'm an end user.
OS.
MacOS Ventura 13.2.1
Browser.
Google Chrome 127.0.6533.101
Is there a workaround for this? I don't have access to edit anything on the backend so I'm hoping there's a way to prevent this from happening strictly using HTML.
The text was updated successfully, but these errors were encountered:
Expected behavior.
Responsive CSS should be able to target elements using classes.
Actual behavior.
Because styles are being inlined, classes are being removed from elements which causes responsive CSS code to no longer work.
Steps to reproduce the problem.
Use the following code in the editor. In my case the code changes after the code is rendered.
The following code is what I enter into the editor.
Then it's rendered as this:
Editor version.
I don't know it. I'm an end user.
OS.
MacOS Ventura 13.2.1
Browser.
Google Chrome 127.0.6533.101
Is there a workaround for this? I don't have access to edit anything on the backend so I'm hoping there's a way to prevent this from happening strictly using HTML.
The text was updated successfully, but these errors were encountered: