Hello all
The First thing every one notices when you start Firefox for the first
time Is how Simple it is to use. Operator works nicely with Firefox
because it too is simple and easy to use, especially when you use it as
an icon in the location bar, you dont even know its there until you
visit a
Alex Faaborg skrev:
This is a bit of a hack, but it is also considerably easier than
asking the author to write javascript to check navigator.userAgent,
know which browsers handle microformatted content (and subsequently
update this as it changes), and then display the link accordingly.
Not sure I quite understand this (so a good example of a general
'blogger' wanting to put uf on their blog/site), are you saying that the
blogger/webmaster is deciding the actions rather than fx3 or an Operator
like extension. Using your example code, would I be required to put in a
multitude of
are you saying that the
blogger/webmaster is deciding the actions rather than fx3 or an
Operator
like extension.
No, the browser should still act as a mediator between data and
applications, otherwise people will tie there information to
particular apps (like what is currently happening
In message [EMAIL PROTECTED], Alex
Faaborg [EMAIL PROTECTED] writes
The last class is new:
div class=user-action style=visibility:hiddenAdd to Address
Book/div
The text Add to Address Book is hidden by default, unless the browser
(or an extension) recognizes user-action
...or unless the
Instead of having to checking whether the userAgent is right or
wrong in my javascript - wouldn't it be possible to check for the
presence of any hCard-related function instead?
Yeah, if we wanted to solve this problem with javascript, that is
probably what we should do. But I'm a little
André Luís skrev:
One thing I need someone to clarify:
Is that div.user-action inserted by the user-agent, in this case,
Firefox 3? Or do the authors have to include that code on their pages?
This wasn't very clear to me...
I've understood that it's inserted by the web developer to enable
I've understood that it's inserted by the web developer to enable
him/her to implement the Microformat-actions in their own designs
and it's suggested that the class user-action should be used to
indicate that something is meant to be a link to such an action.
Yes, while previous Firefox
On Aug 28, 2007, at 6:33 AM, Alex Faaborg wrote:
Yes, while previous Firefox designs have focused on the browser
injecting UI into the page, this discussion is about how the
content creator should provide links and buttons for acting on
microformatted content.
It seems you'll still need
Perhaps instead of new classes and protocols, we could just do this
completely in javascript. Here is a general example, probably all
the function names would end up being different:
div id=hcard-Alex-Faaborg class=vcard
span class=fnAlex Faaborg/span
div class=orgMozilla/div
div
Alex Faaborg wrote:
Yes, while previous Firefox designs have focused on the browser
injecting UI into the page, this discussion is about how the content
creator should provide links and buttons for acting on microformatted
content.
I'm probably being a bit dense, but it looks like we're
This idea is really good, the best possible I think.
If there is a need for interaction on a website then the options are
limited to the browser UI and the script languages available, right?
And this way you're suggesting the user will have the possibility of
adding their own interaction with
Manu Sporny wrote:
Here are some other examples:
action://map/find/eiffel-tower
action://
Sorry, here are the other examples:
action://location/find/eiffel-tower
action://license/fulltext/Harry-Potter-and-the-Order-of-the-Phoenix
action://feed/subscribe/cool-hatom-feed
My apologies if I'm reopening a long closed debate, I'll be sure to
review the wiki page.
Side A: Publishers should be able to specify UI elements for their
Microformatted content in their HTML.
Side B: The browser should be solely responsible for injecting UI into
the page
I should note
Sorry for the long delay in posting an update to this thread, we are
still working on finalizing the UI for interacting with microformats
in Firefox.
Here is something Mike Beltzner, Mike Kaply and I have been
considering for microformat handling in Firefox 3, in terms of the
content
did you carry on working on the idea of showing whats a microformat in
the page? There was talk of a mouse cursor change when a user hovers
over. The last mockup i saw had an icon at the end of the address bar
with action. I think both of those would be a good way forward.
I started a thread
16 matches
Mail list logo
