This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Example CSS (style sheet) class: example-class { top: expression(offsetParent.scrollTop); } A syntax error is reported at the semicolon. Syntax highlighting stops working after that point, and Style Builder is unavailable. NetBeans ought to be more lenient here, even if that syntax is not W3C-standard. See http://msdn2.microsoft.com/en-us/library/ms537634.aspx for a description of expression() values. Found with build 200707171200.
*** Issue 127699 has been marked as a duplicate of this issue. ***
In issue 127699 jsedek writes that this issue is going to be fixed for 6.1. I'd just like to point out that the target milestone is still set to "future".
I'll fix this one to 6.1
still valid. I'll update the css grammar to be able to parse the non-w3c format and add some warnings annotations to such code.
*** Issue 123266 has been marked as a duplicate of this issue. ***
moving opened issues from TM <= 6.1 to TM=Dev
from issue 133277: I believe I was mistaken in my description of this error. Those CSS properties I list above are proprietary IE properties; compatible with IE5.5 and greater. See here: http://eis.bris.ac.uk/~cckhrb/webdev/code/css/scrollbar.htm and here at Microsoft's site: http://msdn2.microsoft.com/en-us/library/ms531155(VS.85).aspx As far as I can tell, they aren't new properties added for CSS3, just specific to IE. Maybe we need a config menu, like the JavaScript one, for CSS too? This would also change the focus of this defect from CSS3 compliance, which I think is also important. Maybe someone else could open one for that enhancement? Thanks again for your help, mfukala.
*** Issue 133227 has been marked as a duplicate of this issue. ***
css grammar enabled to support M$ expression syntax. http://hg.netbeans.org/main/rev/3d4ac2f6e861
Since the embedding model may change in 6.5 by adopting the new parsing API from planar to transitive I will wait with implementing the embedding model for javascript embedded in css expressions() till it is clearer what will happen.
I found one more case supported for IE: filter: alpha(opacity=50) - it also shouldn't be marked as an error but maybe just warning of non portability could be shown
*** Issue 138428 has been marked as a duplicate of this issue. ***
*** Issue 142258 has been marked as a duplicate of this issue. ***
Add my vote for not marking the "filter:" syntax as an error. It would also be nice to have some "suppress warnings" mechanism to selectively suppress warnings on browser-specific syntax elements.
MS CSS extensions: http://msdn.microsoft.com/en-us/library/ms531207.aspx Firefox extensions: http://developer.mozilla.org/En/CSS_Reference:Mozilla_Extensions
another example: h1 { filter: progid:DXImageTransform.Microsoft.Blur( PixelRadius=5,MakeShadow=true,ShadowOpacity=0.20); }
Another sample: filter:alpha(opacity=50);
*** Issue 158886 has been marked as a duplicate of this issue. ***
Updated TM.
*** Issue 172939 has been marked as a duplicate of this issue. ***
*** Issue 168406 has been marked as a duplicate of this issue. ***
*** Issue 171564 has been marked as a duplicate of this issue. ***
another examples from duplicated issues: h1 { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='trans.png', sizingMethod='scale'); } div.component-tools { filter:alpha(opacity=50); opacity:0.5; display:block; } #content>.content>.product>p.title { position: relative; top: -35px; background-color: white; filter: progid:DXImageTransform.Microsoft.Alpha(opacity=70); -moz-opacity: 0.7; -khtml-opacity: 0.7; opacity: 0.7; }
fixed in web-main
#cf03f3c97c36