W3C home > Mailing lists > Public > www-style@w3.org > April 2005

Re: Style confirmation descriptors

From: Mikko Rantalainen <mikko.rantalainen@peda.net>
Date: Thu, 07 Apr 2005 12:29:01 +0300
Message-ID: <4254FD5D.4060208@peda.net>
To: www-style@w3.org

Barry wrote:
> Create a language that describes how a part of the webpage should look at a 
> certain resolution and change the CSS accordingly, for example:
> 
> DisplayTry {...}
> DisplayCheck {res: 1024,768; loc: 100,200,150,250; direction: l,r; find: 
> border; text; red; end;}
> FoundReplace {...}
> UnfoundReplace {...}

You already made it pretty clear that you didn't read the existing 
specs. May I ask you to read at least enough to understand the 
existing syntax? That would make it much easier to understand the 
ideas you or anybody else is trying to suggest.

I decipher that you're asking for following construct (I'm not sure 
if even this @verify block is possible within existing parsing rules):

@try { ... }
@verify {
  resolution: 1024px,768px; /* Is this display resolution? Why? */
  direction: l,r; /* What is this? What do you need it for? */
  search-area: 100px, 200px, 150px, 250px;
  search-target: border; /* how do you define 'border'? */
  text: ; /* CANNOT DECODE */
  red: ; /* CANNOT DECODE */
  end: ; /* CANNOT DECODE */
}
@if-last-verify-failed
{
	... /* new rules to try again */
}
@verify
{
  ... /* check if it's now okay */
}

Should the rules in @if-last-verify-failed be in addition to rules 
in @try or should rules in @try block be totally discarded?

-- 
Mikko
Received on Thursday, 7 April 2005 09:29:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:36 GMT