2. Microformats are in page, and there needs to be some way
to indicate the microformats are available on the page that
doesn't offend page authors. How can we accomplish this?
I second the opinion that this is a design issue and therefore should be
handled by css in some way. This would
Farndon, Tony skrev:
2. Microformats are in page, and there needs to be some way
to indicate the microformats are available on the page that
doesn't offend page authors. How can we accomplish this?
I second the opinion that this is a design issue and therefore should be
handled by css in
If something should add anything it should be added by a
javascript...
CSS is frequently used to *add* and place onto a page, be it a
background image, a border, etc
What I am saying is rather than add say, a background image, you use CSS
to add/place a microformat icon. How this icon behaves
Hello everyone.
Great work thus far.. just want to drop my 2cents.
1) I don't think Dimitri's text was very clear on this aspect in
particular, but I believe it would improve the UXP and still give
control to the publisher.
Why not mixing the suggestion of dimitry (which seems like a very
To try and give where I am coming from some context, this is how I see
it all working in my head:
FF3 has a set of (3?) methods for alerting/displaying/provding actions
for uF
1) An Operator style toolbar
2) An Operator Style status icon
3) Within the content of the page (+1 and then some for
On 9/5/07, André Luís [EMAIL PROTECTED] wrote:
Hello everyone.
- when the user hovers on the margin-mark, the user-agent should
'target' to the (root?) element (like what's done with the #anchor in
urls) and that would allow the publishers to specify the
looks/highlight accordingly. Like:
Thanks for the comments on the margin-marks concept. I sincerely
appreciate that.
I really like the idea of allowing additional control over
presentation via pseudo-classes, but I am worried that :target isn't
quite right, at least if we follow the spec to the letter
Thanks for the comments on the margin-marks concept. I
sincerely appreciate that.
Credit where credit is due!
I really like the idea of allowing additional control over
presentation via pseudo-classes, but I am worried that
:target isn't quite right, at least if we follow the spec to
Dimitri,
That was exactly why I suggested :target instead of :focus. I think
ufs shouldn't _require_ links or other focus-eable elements. And I'm
with you with the worries on pushing the meaning of the spec... is
there a more meaningful alternative I don't know about?
And I'm with Tony (and
And I'm with Tony (and others) on the protocol approach.
I should, however, add that I do have one concern about the protocol
approach; it does not degrade gracefully. Users of FF2, or IE7 or Safari
etc will just get a big old unknown protocol error.
This is easily countered by the designer
Farndon, Tony wrote:
And I'm with Tony (and others) on the protocol approach.
I should, however, add that I do have one concern about the protocol
approach; it does not degrade gracefully. Users of FF2, or IE7 or Safari
etc will just get a big old unknown protocol error.
This is easily
Alex Faaborg wrote a clever mail about this earlier and
presented a few issues and a few possibilites related to
protocols. It was then discussed that perhaps there should be
one protocl for each microformat?
That would if so enable different programs to easily take
care of different
I think some folks here are missing the point in the
Microformats/Firefox 3 discussion.
We are trying to foster a discussion about what to do with
microformats in Firefox 3, we are not trying to tell you what we are
going to do.
This is a very difficult problem to solve and we need input on it.
Ok Mike. Thanks for clearing it up.
I'd like to know one thing... Have you discussed the option of using
the notification box as a first notification to the user of the
presence of microformats in the current page and _there_ provide a
button to reveal them?
I've searched but found nothing
Mike,
I must say the way I'm using Operator in Flock Firefox at the moment
(using the auto-hide function for the toolbar) is working well for me.
I think one way to go is to utilize the same functionality as the
this site wants to open pop-up windows that Firefox has. A small
toolbar-like
On 9/4/07, David Mead [EMAIL PROTECTED] wrote:
I would love to see a new button in the URL bar, like Flock has for
when there is RSS, media streams or a SE plugin on the page. That is
one feature of the new Flock I find I'm using a lot now.
Note that Operator does have a URL button option in
On 9/4/07, Mike Kaply [EMAIL PROTECTED] wrote:
I think some folks here are missing the point in the
Microformats/Firefox 3 discussion.
We are trying to foster a discussion about what to do with
microformats in Firefox 3, we are not trying to tell you what we are
going to do.
This is a very
Dimitri Glazkov wrote:
This is not particularly transient, but it addresses #2, methinks:
http://glazkov.com/blog/margin-marks/
Mike, Alex - I think you should take a very serious look at Dimitri's
Margin Marks idea. Check out the screen mock-ups here:
I really like this idea, I just forward the post and mockups to the
rest of our UX team and our lead engineer.
This is not particularly transient
If the margin marks bar only appeared on pages with recognized
content, then I think this would certainly count as being transient.
Or, to
On 9/4/07, Alex Faaborg [EMAIL PROTECTED] wrote:
I really like this idea, I just forward the post and mockups to the
rest of our UX team and our lead engineer.
I agree with Alex. This is a really great idea.
Thanks for posting.
Mike
___
20 matches
Mail list logo
