Closed Bug 304497 Opened 19 years ago Closed 18 years ago

RSS not accessible

Categories

(Firefox :: Keyboard Navigation, defect, P3)

2.0 Branch
defect

Tracking

()

RESOLVED FIXED
Firefox 2 beta1

People

(Reporter: aaronlev, Assigned: pilgrim)

References

Details

(Keywords: access, fixed1.8.1, Whiteboard: [l10n impact])

Attachments

(1 file, 3 obsolete files)

There is no way to get the RSS view of a page with the keyboard.

There is no indication to screen reader users that an RSS view exists for a page.
A context menu item would do.
Flags: blocking1.8b4?
Whiteboard: [possible l10n impact]
Target Milestone: --- → Firefox1.1
Okay, maybe a context menu item would be okay, but how does a screen reader user
know to look there? You're not going to check the context menu for every page
you visit.
Did we have anything useful for live bookmarks upon now? (The old statusbar
element)?
(In reply to comment #3)
> Did we have anything useful for live bookmarks upon now? (The old statusbar
> element)?

No, it slipped by my notice earlier.
Anyone have a suggestion on this one, other than a context menu entry?
Beltzner had some in Bug 303848 comment 40.
Per Bug Meeting 8/16 Can we implement suggestion #2 in <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=303848#c40">303848c40</a> -
i.e. add a Feeds/RSS tab to the page info.   
Assignee: nobody → mconnor
Flags: blocking1.8b4? → blocking1.8b4+
Flags: blocking1.8b5+
I think that Aaron and I were happier with the first solution mentioned in bug
303848 comment 40, specifically adding the RSS icon to the TAB key sequence.
While this sol'n has the drawback of breaking muscle memory for users who are
accustomed to using Ctrl+L, tab to get to the search bar, those users a) form a
small subset of the overall user base and b) should be using Ctrl+K to get there
directly anyway.
So, after much discussion, the tab sequence isn't practical, for the same reason
that we can't focus the searchbar icon, we can't focus these.

What we're proposing is to add this to the Bookmarks menu, like so:

[Bookmarks]
___________________________
|Bookmark this Page...    |
|Add as Live Bookmark...  |
|Bookmark All Tabs...     |
|Manage Bookmarks         |
|-------------------------|

[Bookmarks]
___________________________
|Bookmark this Page...    |________________________
|Add as Live Bookmark    >| Mozilla Announcements |
|Bookmark All Tabs...     | Mozilla Weblogs       |
|Manage Bookmarks         |------------------------
|-------------------------|

Will get on this once the feedview backout is done.
Just playing devil's advocate here. Just because a users wants to view the RSS
feed directly does that necessarily mean they want to bookmark it? If that's the
case, then why doesn't the RSS button in the URL bar go straight to a bookmark
options popup menu. Why did we do all the work of having making the feed
viewable as content?
(Feedview was backed out in bug 305134)

Couple of suggestions/nits ..:
 - "Add Live Bookmark..." (drop the "as")
 - the flyout text should be "Add &feedName;..."

so ..:

[Bookmarks]
___________________________
|Bookmark this Page...    |
|Add Live Bookmark...     |
|Bookmark All Tabs...     |
|Manage Bookmarks         |
|-------------------------|

[Bookmarks]
___________________________
|Bookmark this Page...    |______________________________
|Add Live Bookmark       >| Add Mozilla Announcements... |
|Bookmark All Tabs...     | Add Mozilla Weblogs...       |
|Manage Bookmarks         |------------------------------
|-------------------------|
Note that bug 251447 has some healthy discussion about how to get the best "feed
name" from a feed, although I don't think any of those should block release, and
am happy with the simplest case of using:

  - the "title" attribute from the <link rel> tag for cases where we need to
    differentiate between multiple feeds on a page

  - a combination of "page title - title attribute" for the default Live Bookmark
    name (as mentioned in bug 305799)
Attached patch first cut (obsolete) — Splinter Review
Attachment #193998 - Flags: review?
Attachment #193998 - Flags: review?
Attached patch patch (obsolete) — Splinter Review
Minimal impact on l10n, the wording in the multiple-feed submenu isn't ideal,
but it's sharing code with the menupopup for the URL bar button.  Could fix
that as a followup, but that's a bit more code and more l10n work.

This is well-tested and should be safe for branch once it has review.
Attachment #193998 - Attachment is obsolete: true
Attachment #194075 - Flags: review?(vladimir)
Whiteboard: [possible l10n impact] → [possible l10n impact][needs review vlad]
Comment on attachment 194075 [details] [diff] [review]
patch

Bleh, I still think that having this "Add Live Bookmark" menuitem right there
is going to be very confusing to any user that doesn't know exactly what a live
bookmark is.  When confronted with "Bookmark this page" and "Add Live
Bookmark", what are they going to choose?    "Live Bookmark" certainly sounds
better, but it won't be enabled on the majority of pages out there.  I guess
they have to add a dead bookmark then?	However, I don't have a better
solution. =/

r=vladimir, with UI grumbling..
Attachment #194075 - Flags: review?(vladimir) → review+
Attachment #194075 - Flags: approval1.8b4?
fwiw, I agree almost completely (almost!), but we didn't have time to come up
with a more ideal solution. For future, I'd really like to sit and talk with you
about bookmarks, rss / live bookmarks, and ways we can synthesize these various
things to simplify the story to our users.
Attachment #194075 - Flags: approval1.8b4? → approval1.8b4+
Comment on attachment 194075 [details] [diff] [review]
patch

Vlad suggests we just add a keyboard shortcut to bring up the menu from the
live bookmarks icon in the addressbar. that would be much lower impact and
since we don't have "the right" solution here, I think that'd be a better way
to go as well.
Attachment #194075 - Flags: approval1.8b4+
Let's take a step back and examine the whole RSS UI.  The menuitem, with the
exception of being visible when there's no feeds, is the same what we have in
the URL bar, down to the tooltip and label being identical.  If that UI is ok,
the menuitem is ok, but if its not, then the menuitem sucking is a paralell of
our sucky RSS UI.  If "Add Live Bookmark..." is going to confuse users, then we
already fail that user with the current UI (and the UI for 1.0).

For 2.0 we need to rethink how we present feeds to the user, but right now we're
not at that point.  Its not the time, or the point in the cycle, where we
rethink a whole chunk of UI.

As for the keyboard shortcut to trigger the submenu/dialog instead of adding a
menuitem, that has some other problems.
1) Requires the URL bar be present.
2) Not at all discoverable (Help is only useful in this case if the user divines
that its signalling something and manages to guess right.)
3) This is pretty much a toolbar icon, whether its included inside of another
element, its a separate feature from the action of the address bar, and ergo not
having a menuitem probably violates all of the HIGs that require menu items to
be available for each toolbar item.  (Last time I looked this up, it was
Windows, Mac, and GNOME.)
Whiteboard: [possible l10n impact][needs review vlad] → [possible l10n impact]
Minusing this for now for beta1/beta2.   We should re-examine when we have more
time to determine the ideal solution.
Flags: blocking1.8b5-
Flags: blocking1.8b5+
Flags: blocking1.8b4-
Flags: blocking1.8b4+
I understand that we can declare that this is not an accessible feature and
still achieve sec508 certification.
Well, then that's what we should do, since the alternative solutions at this
time (Page Info, adding it into the tabkey-focus order) are all similarly
unpalettable.

I suppose this another one to add to my growing list of "let's investigate this
a little bit to see what people expect." In the meantime, if we can get away
with *just* the URL bar icon and still be s.508 compliant, I think that's the
best choice UI-wise for the beta releases.

(note: Regarding Vlad's UI grumblings, while I understand that it's entirely
possible that a user might find the idea of a "Live Bookmark" more palettable
than a regular ol' bookmark, I'm not convinced that's a bad thing. After all,
"Live Bookmarks" are much more useful in many cases. This is an area for much
heated debate, I'd wager!)
a related one - 306882.

> As i understand currently the Feedview icon in the status bar has been removed
> (?)(for Firefox 1.5).  This leaves a user with only one option of using the
> subscribe to feed button in the location bar for adding one Live Bookmark to his
> bookmarks list.  Mostly I use Firefox with no toolbars to conserve space and
> view more and uses keyboard for most of the navigation.  That leaves me with no
> option to easily add such a feed to bookmark.  As far as I think there is no
> other way.
> 

There is no option for a user to know that a page contains live feeds, which
could be bookmarked.  So the feedview icon in the status bar is one good
alternative to indicate this.  Along with this a menu item Feeds...<expanding to
 available live feeds on the page> under the 'View' menu (?)

The individual links from the feed(s) should be expanded the way it is done with
any live bookmark under Bookmarks menu, so that they are independently viewable.
 The last item of the feeds could be 'Add as Live Bookmark...'

[View]
___________________________
|.........................|_____________________ _____________________
|RSS Feeds               >| Feed 1             >|Item 1              | 
|.........................| Feed 2             >|Item 2              |
|.........................|---------------------|Item 3              |
|-------------------------|                     |--------------------|
                                                |Add as Live Bookmark|
                                                ----------------------

Similar behaviour should be shown by the Feedview icon of URL Bar.
Severity: normal → major
Target Milestone: Firefox1.5 → Future
Mconnor says we should target this one for Firefox 1.5.1
Target Milestone: Future → Firefox1.5
(In reply to comment #23)
> Mconnor says we should target this one for Firefox 1.5.1
> 

Suggestion:

Maybe an entry in the "View" menu? 
Example:
"View" > ...
         Page Source Ctrl+U
         Page RSS     
         Full Screen F11

After all, isn't the bug about getting the RSS View of the page instead of subscribing to the RSS feed?
Not sure I like the solution in comment #22 because it involves requesting all the feed links to be able to show the items.

#24 I like better - but perhaps a submenu?

View >
   Page Source Ctrl+U
   RSS Feed(s) >
      Page Title - Link Title 1
      Page Title - Link Title 2
      ...
   Full Screen F11

Bookmarks >
   Bookmark This Page...
   Bookmark This (These) RSS Feed(s) >
      Page Title - Link Title 1
      Page Title - Link Title 2
      ...
   Bookmark All Tabs...
Flags: blocking-firefox2?
Perhaps
   Bookmark (An) RSS Feed >
would be more accurate than
   Bookmark This (These) RSS Feed(s) >

since the user can only bookmark a single feed at a time.
Flags: blocking-firefox2? → blocking-firefox2+
(In reply to comment #24)
> "View" > ...
>          Page Source Ctrl+U
>          Page RSS     
>          Full Screen F11

View isn't really an appropriate place for this, as RSS isn't neccessarily an alternate view of the content, nor is RSS a function that changes the way the browser presents itself to the user.

This bug might end up getting swallowed up by the work being done on "Places" (see: http://wiki.mozilla.org/Places) which is tracked by bug 317841.
Priority: -- → P3
Target Milestone: Firefox1.5 → Firefox 2 beta1
Status: NEW → ASSIGNED
Assignee: mconnor → dietrich
Status: ASSIGNED → NEW
Is the current Places UI accessible? If not, would it be easier to fix than with the old bookmarks stuff (as discussed in this bug) ?
I believe this bug is on hold until the Places UI stabilizes, and then we're going to fix it in Places.
Status: NEW → ASSIGNED
Assignee: dietrich → pilgrim
Status: ASSIGNED → NEW
If this bug is places only, it shouldn't target fx2b1, right?
Its not places-only.
Attached patch patch for 1.8 branch (obsolete) — Splinter Review
Implement menu item in Bookmarks menu called "Subscribe To This Page" (MOZ_FEEDS) or "Add Live Bookmark" (!MOZ_FEEDS).  If page has multiple feeds, menu item will expand to show all choices, just like clicking the feed icon in the location bar.  Selecting a feed will show the feed view (MOZ_FEEDS) or add a live bookmark (!MOZ_FEEDS).
Attachment #194075 - Attachment is obsolete: true
Attachment #225720 - Flags: ui-review?
Attachment #225720 - Flags: review?(mconnor)
Attachment #225720 - Flags: ui-review? → ui-review?(beltzner)
Comment on attachment 225720 [details] [diff] [review]
patch for 1.8 branch

Nit:

>+<!ENTITY subscribeToPageMenupopup.label "Subscribe To This Page">
>+<!ENTITY subscribeToPageMenuitem.label "Subscribe To This Page...">

If we have "Search in Bookmarks" below (with 'in' being lowercase), I think that the 'to' should be lowercase, also.

...
...
> <!ENTITY searchBookmarksCmd.label "Search in Bookmarks...">

Just my two cents.
Comment on attachment 225720 [details] [diff] [review]
patch for 1.8 branch

Right now I'm seeing what is a bug, and I can't tell if it's local to my tree (which I pulled a couple of days ago) or not, but I get both "Subscribe to This Page" and "Subscribe to This Page >" options with the former always disabled and the latter always enabled.

Anyway, Mark tells me the intended UI is to have one or the other based on the number of available feeds, so this gets ui-r+ :)
Attachment #225720 - Flags: ui-review?(beltzner) → ui-review+
Fixed beltzner's Mac issue by using the proper XUL attribute (hidden instead of collapsed) to hide the menu item we're not currently using.

Also fixed the capitalization of the word "to".
Attachment #225720 - Attachment is obsolete: true
Attachment #225765 - Flags: review?(mconnor)
Attachment #225720 - Flags: review?(mconnor)
Comment on attachment 225765 [details] [diff] [review]
Use hidden instead of collapsed for Mac compatibility

So, this looks good, though I think I wrote most of this, so I'm naturally biased!
Attachment #225765 - Flags: review?(mconnor) → review+
(In reply to comment #36)
> So, this looks good, though I think I wrote most of this, so I'm naturally
> biased!

Yup, you did.  I just updated the patch-rot and fixed a bug or two.
Status: NEW → ASSIGNED
Whiteboard: [possible l10n impact] → [l10n impact], [checkin needed]
Checked in, branch and trunk.

mozilla/browser/locales/en-US/chrome/browser/browser.dtd 	1.25.2.20
mozilla/browser/base/content/browser.js 	1.479.2.150
mozilla/browser/base/content/browser-menubar.inc 	1.57.2.35

mozilla/browser/locales/en-US/chrome/browser/browser.dtd 	1.48
mozilla/browser/base/content/browser.js 	1.644
mozilla/browser/base/content/browser-menubar.inc 	1.95
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Keywords: fixed1.8.1
Hardware: PC → All
Resolution: --- → FIXED
Whiteboard: [l10n impact], [checkin needed] → [l10n impact]
Version: unspecified → 2.0 Branch
Blocks: 341888
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: