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

Re: Why Binding Scripting in Style Layer Conflates Semantics

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Wed, 23 Nov 2005 23:32:23 -0800
Message-ID: <012b01c5f0c9$35f50530$3201a8c0@Terra>
To: <shelby@coolpage.com>, <www-style@w3.org>

----- Original Message ----- 
From: "Shelby Moore" <shelby@coolpage.com>

> Andrew Fedoniouk wrote:
>> What I shall do if I will get <mapselect> which is
>> unknown to my engine, as an example?
>> What is the fallback schema assumed?
> I forgot to address the sub-classing essense of your point.  XAML most
> definitely provides the graceful fallback to base class functionality:
> http://windowssdk.msdn.microsoft.com/library/en-us/wcp_conceptual/html/0ff5f36e-dd84-44d1-aa3e-5bb4f147b169.asp

I didn't find anything there about "graceful fallback" .

> <Canvas
>  xmlns="http://schemas.microsoft.com/winfx/avalon/2005"
>  xmlns:x="http://schemas.microsoft.com/winfx/xaml/2005"
>  x:Class="MyNamespace.MyCanvasCode">
>  <Button Click="Button_Click">Click Me!</Button>
> </Canvas>
> In above example, imagine <Canvas> is a <select>, and MyCanvasCode is
> MapSelect.  Disclaimer, I have not studied this syntax well yet.

To be able to do any fallback UA must be told about class and base class
of the <mapselect>.  This can be accomplished by a) supplying
namespace specific to the domain (a.k.a. type/style sheet) or b)
by using element attributes.

So <mapselect> will get something like

<mapselect type="select">

At this point I would like to know why it is better in principle than:

<select type="mapselect" />


mapselect { behavior: select;  }
<mapselect />



Andrew Fedoniouk.
Received on Thursday, 24 November 2005 07:32:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:21 UTC