Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"webkit-*" vs "-webkit-*" #70

Open
mcjazzyfunky opened this issue Aug 20, 2018 · 6 comments · May be fixed by #116 or #166
Open

"webkit-*" vs "-webkit-*" #70

mcjazzyfunky opened this issue Aug 20, 2018 · 6 comments · May be fixed by #116 or #166

Comments

@mcjazzyfunky
Copy link

mcjazzyfunky commented Aug 20, 2018

It seems there's a problem with the webkit prefixes (leading "-").
I think it should be -webkit-transform, not webkit-transform.

The following code shows the issue:

const
  cssstyle = require('cssstyle'),
  style = new cssstyle.CSSStyleDeclaration();

style.cssText = 'background-color: red; -webkit-transform: scale(2);'

// Be aware: Using "-webkit-transform" with leading "-"
console.log('background-color: ' + style.backgroundColor)  // working => "red"
console.log('-webkit-transform: ' + style.webkitTransform) // not working => "" <---------- !!!!


// Be aware: Using "webkit-transform" now, without leading "-"
style.cssText = 'background-color: green; webkit-transform: scale(3);'

console.log('background-color: ' + style.backgroundColor)  // working => "green"
console.log('webkit-transform: ' + style.webkitTransform) // working => "scale(3)"
@nyroDev
Copy link

nyroDev commented Nov 23, 2023

This issue should be fixed with #112

@nyroDev nyroDev linked a pull request Nov 26, 2023 that will close this issue
@haohongyang1
Copy link

haohongyang1 commented Oct 30, 2024

Hi, I have encountered the same issue in the latest versions of JSDOM and CSSStyle. What is the solution to this problem? @nyroDev Looking forward to your reply, thank you

@nyroDev
Copy link

nyroDev commented Oct 30, 2024

@haohongyang1 I did #166 to fix it, waiting for merge.

@haohongyang1
Copy link

@haohongyang1 I did #166 to fix it, waiting for merge.

Hi @nyroDev I noticed that MR #166 was created in 2023. Do you have an estimated timeline for when it might be merged? Thank you for your efforts on this!

@nyroDev
Copy link

nyroDev commented Oct 30, 2024

@haohongyang1 You should ask the maintainer @domenic

@domenic
Copy link
Member

domenic commented Oct 31, 2024

I am not the maintainer for this library. It's not really maintained; we've had some people join the maintainer team once in a while, but they don't seem to be active anymore. We're seeking someone who is willing to maintain it.

In the meantime, sometimes I do small bugfix releases out of general guilt, but you should not expect reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants