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.

Bug 110333 - [68cat] Microsoft expression() syntax not supported in CSS
Summary: [68cat] Microsoft expression() syntax not supported in CSS
Alias: None
Product: web
Classification: Unclassified
Component: CSS Visual Tools (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker with 2 votes (vote)
Assignee: Marek Fukala
: 123266 127699 133227 138428 142258 158886 168406 171564 172939 (view as bug list)
Depends on: 170728
  Show dependency tree
Reported: 2007-07-19 20:58 UTC by matthies
Modified: 2010-04-14 12:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description matthies 2007-07-19 20:58:23 UTC
Example CSS (style sheet) class:

        top: expression(offsetParent.scrollTop);    

A syntax error is reported at the semicolon. Syntax highlighting stops working after that point, and Style Builder is 

NetBeans ought to be more lenient here, even if that syntax is not W3C-standard.
See for a description of expression() values.

Found with build 200707171200.
Comment 1 Jindrich Sedek 2008-02-19 10:32:45 UTC
*** Issue 127699 has been marked as a duplicate of this issue. ***
Comment 2 matthies 2008-02-19 14:09:41 UTC
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".
Comment 3 Marek Fukala 2008-02-20 13:19:22 UTC
I'll fix this one to 6.1
Comment 4 Marek Fukala 2008-02-25 17:02:44 UTC
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.
Comment 5 Marek Fukala 2008-02-26 11:01:20 UTC
*** Issue 123266 has been marked as a duplicate of this issue. ***
Comment 6 Jiri Prox 2008-04-11 01:05:17 UTC
moving opened issues from TM <= 6.1 to TM=Dev
Comment 7 Marek Fukala 2008-05-14 10:14:16 UTC
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:
and here at Microsoft's site:

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.
Comment 8 Marek Fukala 2008-05-14 10:14:26 UTC
*** Issue 133227 has been marked as a duplicate of this issue. ***
Comment 9 Marek Fukala 2008-05-15 13:33:22 UTC
css grammar enabled to support M$ expression syntax.
Comment 10 Marek Fukala 2008-05-15 13:37:23 UTC
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. 
Comment 11 Jindrich Sedek 2008-05-20 11:26:13 UTC
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
Comment 12 Marek Fukala 2008-08-21 11:40:44 UTC
*** Issue 138428 has been marked as a duplicate of this issue. ***
Comment 13 Marek Fukala 2008-08-21 11:40:54 UTC
*** Issue 142258 has been marked as a duplicate of this issue. ***
Comment 14 matthies 2008-08-21 16:09:21 UTC
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.
Comment 16 Marek Fukala 2008-09-03 14:47:05 UTC
another example:

h1 {
filter: progid:DXImageTransform.Microsoft.Blur( PixelRadius=5,MakeShadow=true,ShadowOpacity=0.20);
Comment 17 Marek Fukala 2009-04-30 10:41:20 UTC
Another sample: filter:alpha(opacity=50);
Comment 18 Marek Fukala 2009-04-30 10:41:36 UTC
*** Issue 158886 has been marked as a duplicate of this issue. ***
Comment 19 matthies 2009-08-20 13:41:54 UTC
Updated TM.
Comment 20 Marek Fukala 2009-09-24 17:17:43 UTC
*** Issue 172939 has been marked as a duplicate of this issue. ***
Comment 21 Marek Fukala 2009-09-24 17:18:20 UTC
*** Issue 168406 has been marked as a duplicate of this issue. ***
Comment 22 Marek Fukala 2009-09-24 17:18:41 UTC
*** Issue 171564 has been marked as a duplicate of this issue. ***
Comment 23 Marek Fukala 2009-09-24 17:18:49 UTC
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;
Comment 24 Marek Fukala 2010-04-14 12:49:27 UTC
fixed in web-main
Comment 25 Marek Fukala 2010-04-14 12:50:22 UTC