I had to install Firefox on my Mac because my e-mail account at
yahoo.com no longer recognizes Safari. My problem mostly with Firefox
is that it is a hard disc hog as well as a RAM hog; and, causes
everthing on the net; and, if it is running in the background, on my
Mac itself, run as slowly as 'molasses in January'; and, I just hate
standing at my computer 'twiddling my thumbs'.

JG

On 8/3/07, James Austin <[EMAIL PROTECTED]> wrote:
> Do you think it's worth giving it a go?
> James
> On 4 Aug 2007, at 00:30, Benjamin Hawkes-Lewis wrote:
>
> > I think it's not only possible, but likely, if anyone comes forward to
> > do the work as Waara did before. As with any project, often bugs
> > remain unfixed in Firefox for a long time because, although everyone
> > is agreed they should be fixed, no-one puts in the time to fix them.
> > And this is quite a large and complex bug.
> >
> > On the other hand, I don't think Fire Vox is particularly expensive in
> > terms of hard disk storage.
> >
> > --
> > Benjamin Hawkes-Lewis
> >
> > On 8/4/07, James Austin <[EMAIL PROTECTED]> wrote:
> >> Ah thank you for explaining it to me Benjamin
> >>
> >> Do you think it is possible that Firefox will one day be VO usuable
> >> without the need for Firvox? I am not aainst speech enabled programs
> >> like this, but it just seems that VO might be able to do it on its
> >> own so saving space on the hard drive.
> >>
> >> Thanks james
> >> On 3 Aug 2007, at 23:50, Benjamin Hawkes-Lewis wrote:
> >>
> >>> Jude's problem with Mozilla Firefox is not the lack of Java Access
> >>> Bridge, but that the nobody has finished exposing Mozilla widgets to
> >>> the Apple Accessibility API that VoiceOver uses to understand
> >>> applications. Here's the relevant bug in the Mozilla bugzilla:
> >>>
> >>> https://bugzilla.mozilla.org/show_bug.cgi?id=157209
> >>>
> >>> Unfortunately for Firefox, HÃ¥kan Waara, who was working on this,
> >>> found
> >>> a job and no longer had time to continue. So currently nobody is
> >>> working on it, as far as I know.
> >>>
> >>> On the other hand, there is Fire Vox, as James mentioned, an
> >>> extension
> >>> that turns Firefox into a talking browser, and that does work on Mac
> >>> OS X. The homepage is:
> >>>
> >>> http://www.firevox.clcworld.net/
> >>>
> >>> In answer to James's question, what Firefox can do that Safari and
> >>> Shiira cannot is essentially a limitless set because, unlike
> >>> Safari or
> >>> Shiira, Mozilla provides a plugin framework and it has an active
> >>> plugin community:
> >>>
> >>> https://addons.mozilla.org/
> >>>
> >>> In addition, the Gecko engine that underpins Firefox supports web
> >>> technologies that WebKit, the engine underpinning Safari or Shiira,
> >>> does not as yet. These technologies include MathML (a markup
> >>> language
> >>> for mathematical content) and ARIA (an enhancement to XHTML to make
> >>> Ajax widgets more accessible).
> >>>
> >>> Firefox also has rudimentary support for some basic HTML features
> >>> that
> >>> Safari and Shiira do not have. For example, Firefox provides some
> >>> access to the longdesc attribute for images; Safari and Shiira do
> >>> not.
> >>> Again, Firefox provides some access to the cite attribute of
> >>> quotations, Safari and Shiira do not.
> >>>
> >>> --
> >>> Benjamin Hawkes-Lewis
> >>>
> >>> On 8/3/07, James Austin <[EMAIL PROTECTED]> wrote:
> >>>> Hi,
> >>>>
> >>>> There is something called Fire Revox. It is as far as I understand
> >>>> it, a speech interfce for Firefox. Can i ask though out of
> >>>> curiosity,
> >>>> does Firefox do something that Safari or Shiira does not?
> >>>>
> >>>> Thanks James
> >>>> On 3 Aug 2007, at 22:15, Jude DaShiell wrote:
> >>>>
> >>>>> It may get better for me later this weekend, but for now I
> >>>>> recommend mac users who use voiceover stay with safari.  It could
> >>>>> be that needs java access bridge which so far as I know isn't
> >>>>> on my
> >>>>> mac yet.  When I started firefox up an import wizard came up and I
> >>>>> haven't been able so far to either read it or get beyond it.
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
> >>
>
>
>

Reply via email to