- re-introduce fi:styling/type='date' to explicitely call the template, but now ignoring any possible formatting pattern (since we know it from the widget's datatype)
IIUC, you propose that fi:datatype has no influence on the chosen styling, but gives the format _when_ fi:styling/@type="date" is present, right?
Then a big +1000 !
Having the style driven by both the datatype and styling type will lead to an incredible combinational mess, which we just start to see with this conflict between @type="output" and fi:datatype.
fi:styling/@type chooses the styling, which can then use some additional information such as fi:datatype to fine tune the widget's representation.
If we agree that only fi:styling/@type drives the rendering type, then let's do it right now.
I remember that it was me who asked for simple datatype driven styling of date fields - and Bruno added the datatype feature in that way. Otherwise you always have to add styling/@type="date" to the template. I guess the datatype has no influence on fi:styling?
Joerg
