Adam Scheinberg wrote:
> If either of your scenarios were actually the case,
Mike, then I
> would've expected someone - anyone - to say "Hey,
we hear ya, but it
> wasn't ready in time," or even "There are
technical limitations which
> make this behavior undesirable."
Actually Mike's point is exactly on target, and was
suggested by Robert
earlier as well, *plus* was what I was trying to allude to:
doing this
right is hard, but it's worth doing. Our current behavior
most
certainly isn't perfect.
> BUT... RSS is for tech savvy folks, and will be for
some time.
The entire point of providing a consistent user experience
is to make
this statement untrue. We should not use the realm of
Geekdom as an
excuse to do something unsuitable for "normal
folks", but rather try and
create a solution which solves normal people's problems
while still
being acceptable to the geeks. I continue to harp on
"what do you
actually want to accomplish" not because I'm trying to
justify our
current solution but because I'm trying to step back from
the "you
should obey my stylesheet!" low-level solution and
figure out what the
high-level issue really is.
I don't think people are "not backing down for pride's
sake". I think
there are real UE questions to answer here, on both sides,
that perhaps
neither side understands well. At least on the side of the
developers,
the Fx2 behavior was not viewed to be a major step backwards
because, as
mentioned previously, few sites styled feeds, and most of
those did it
only to guide users back to the main page, not actually in
an attempt to
get users to interact directly in a web browser. I'm a bit
suspicious
that the ranting online consists of a very small
non-representative
sample, plus a lot of people ready to jump on a bandwagon
because
phrases like "defies standards" and
"eliminates choice" are used.
However, just as the stylesheet-advocates need to understand
the
developers' perspective, the developers need to understand
the
legitimate complaints raised against the current behavior.
So, in that
vein: does the idea of a sanitized CSS sink sound appealing?
Or is the
XML+XSLT "I do it all myself" approach the only
acceptable way?
PK
_______________________________________________
dev-apps-firefox mailing list
dev-apps-firefox lists.mozilla.org
h
ttps://lists.mozilla.org/listinfo/dev-apps-firefox
|