I have begun experimenting with some CSS 3 effects , particularly box rounding and box shadows. All of the example I see indicate that I have to use css properties like: border-radius : 25px; -moz-border-radius : 25px; /* Firefox 3.6 and earlier */ -moz-box-shadow : 10px 10px 5px #888888; /* Firefox 3.6 and earlier */ -webkit-box-shadow : 10px 10px 5px #888888; box-shadow : 10px 10px 5px #888888; This causes problems with the W3C CSS validator connected to Oxygen. Is there any way to validate these properties so that my CSS stylesheet does not show errors? Thanks, Mark
Hi Mark, Oxygen 13 which will be released in a couple of days will allow you in the CSS Validator Preferences page to specify a set of property patterns which will be excluded by the validation. So if you will add a pattern like this "-moz*,-webkit*" then the validation will no longer complain about the mozilla and webkit properties. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 8/26/2011 7:17 AM, Mark wrote:
I have begun experimenting with some CSS 3 effects , particularly box rounding and box shadows. All of the example I see indicate that I have to use css properties like: border-radius : 25px; -moz-border-radius : 25px; /* Firefox 3.6 and earlier */ -moz-box-shadow : 10px 10px 5px #888888; /* Firefox 3.6 and earlier */ -webkit-box-shadow : 10px 10px 5px #888888; box-shadow : 10px 10px 5px #888888; This causes problems with the W3C CSS validator connected to Oxygen. Is there any way to validate these properties so that my CSS stylesheet does not show errors? Thanks, Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
That is great! Thanks, Mark -----Original Message----- From: Radu Coravu Sent: Friday, August 26, 2011 1:17 AM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] CSS3 Hi Mark, Oxygen 13 which will be released in a couple of days will allow you in the CSS Validator Preferences page to specify a set of property patterns which will be excluded by the validation. So if you will add a pattern like this "-moz*,-webkit*" then the validation will no longer complain about the mozilla and webkit properties. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 8/26/2011 7:17 AM, Mark wrote:
I have begun experimenting with some CSS 3 effects , particularly box rounding and box shadows. All of the example I see indicate that I have to use css properties like: border-radius : 25px; -moz-border-radius : 25px; /* Firefox 3.6 and earlier */ -moz-box-shadow : 10px 10px 5px #888888; /* Firefox 3.6 and earlier */ -webkit-box-shadow : 10px 10px 5px #888888; box-shadow : 10px 10px 5px #888888; This causes problems with the W3C CSS validator connected to Oxygen. Is there any way to validate these properties so that my CSS stylesheet does not show errors? Thanks, Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi Radu, Thanks for the information about CSS 3 and Oxygen 13. Here's something to think about for your next version: When generating XHTML from XSLT, a JavaScript element requires content (in this case a blank space) in order to load J-Query: <script type="text/JavaScript" xml:space="preserve" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"> </script> [Note space between > </script>] If I do not put the space in, I always get a "J-Query did not load" error. In order to do this, I have to set my preferences to produce ugly double tags for "empty" elements instead of neat <..../> single tag elements. It would be great if I could specify <script> elements to be produced with double tags and a space "<script....> </script>" and all other "empty" elements as <x.../> I used to have some sort of problem validating <meta> tags produced via XSLT, but I no longer remember what it was or if the "double tag" hack solved it or not. Mark
Hello Mark, What kind of output method are you using in your stylesheets? Specifying "html" would make the XSLT transformer create an end tag for the "script" element. However, it does not add a space between tags. If your output documents are XHTML, you do not need the extra whitespace between the tags. From our website: <script src="/js/jquery-1.3.2.js" type="text/javascript" charset="utf-8"></script> Note that the settings for the XML format do not apply on the output that is generated by an XSLT processor. They are used from the Format and Indent action. Regards, Dan On 8/26/2011 12:17 PM, Mark wrote:
Hi Radu,
Thanks for the information about CSS 3 and Oxygen 13. Here's something to think about for your next version:
When generating XHTML from XSLT, a JavaScript element requires content (in this case a blank space) in order to load J-Query: <script type="text/JavaScript" xml:space="preserve" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"> </script>
[Note space between> </script>] If I do not put the space in, I always get a "J-Query did not load" error. In order to do this, I have to set my preferences to produce ugly double tags for "empty" elements instead of neat<..../> single tag elements. It would be great if I could specify<script> elements to be produced with double tags and a space "<script....> </script>" and all other "empty" elements as<x.../>
I used to have some sort of problem validating<meta> tags produced via XSLT, but I no longer remember what it was or if the "double tag" hack solved it or not. Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi Dan, Thanks for calling this to my attention. I just looked at the stylesheet. Apparently, when I was working on this problem a year or so ago, I was "Easter-egging" for a solution. I did not notice that during that period I had set my output to "xml" and never changed it back. Thus, the odd hack with a space. Duh! Thanks, Mark -----Original Message----- From: Dan Caprioara Sent: Friday, August 26, 2011 2:48 AM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] Oxygen 13.1 Hello Mark, What kind of output method are you using in your stylesheets? Specifying "html" would make the XSLT transformer create an end tag for the "script" element. However, it does not add a space between tags. If your output documents are XHTML, you do not need the extra whitespace between the tags. From our website: <script src="/js/jquery-1.3.2.js" type="text/javascript" charset="utf-8"></script> Note that the settings for the XML format do not apply on the output that is generated by an XSLT processor. They are used from the Format and Indent action. Regards, Dan On 8/26/2011 12:17 PM, Mark wrote:
Hi Radu,
Thanks for the information about CSS 3 and Oxygen 13. Here's something to think about for your next version:
When generating XHTML from XSLT, a JavaScript element requires content (in this case a blank space) in order to load J-Query: <script type="text/JavaScript" xml:space="preserve" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"> </script>
[Note space between> </script>] If I do not put the space in, I always get a "J-Query did not load" error. In order to do this, I have to set my preferences to produce ugly double tags for "empty" elements instead of neat<..../> single tag elements. It would be great if I could specify<script> elements to be produced with double tags and a space "<script....> </script>" and all other "empty" elements as<x.../>
I used to have some sort of problem validating<meta> tags produced via XSLT, but I no longer remember what it was or if the "double tag" hack solved it or not. Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Just installed Oxygen 13 and this feature is great! Thanks, Mark -----Original Message----- From: Radu Coravu Sent: Friday, August 26, 2011 1:17 AM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] CSS3 Hi Mark, Oxygen 13 which will be released in a couple of days will allow you in the CSS Validator Preferences page to specify a set of property patterns which will be excluded by the validation. So if you will add a pattern like this "-moz*,-webkit*" then the validation will no longer complain about the mozilla and webkit properties. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 8/26/2011 7:17 AM, Mark wrote:
I have begun experimenting with some CSS 3 effects , particularly box rounding and box shadows. All of the example I see indicate that I have to use css properties like: border-radius : 25px; -moz-border-radius : 25px; /* Firefox 3.6 and earlier */ -moz-box-shadow : 10px 10px 5px #888888; /* Firefox 3.6 and earlier */ -webkit-box-shadow : 10px 10px 5px #888888; box-shadow : 10px 10px 5px #888888; This causes problems with the W3C CSS validator connected to Oxygen. Is there any way to validate these properties so that my CSS stylesheet does not show errors? Thanks, Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
participants (3)
-
Dan Caprioara -
Mark -
Radu Coravu