Frame for firefox does not implement the state "active" when firefox is the active frame (bug 566542 reincarnation)

UNCONFIRMED
Unassigned

Status

()

Core
Disability Access APIs
UNCONFIRMED
6 years ago
6 years ago

People

(Reporter: Nischal, Unassigned)

Tracking

({regression})

11 Branch
x86
Linux
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120310010446

Steps to reproduce:

In gnome desktop environment, we have AT-SPI which is used by assistive technologies. Currently firefox does support accessibility in linux. 

Whenever a frame is the currently activated frame, it takes the state "active" However, when firefox is the currently opened frame it does not assume the state of "active".

This bug was reported earlier(https://bugzilla.mozilla.org/show_bug.cgi?id=566542) but was fixed in an older version of firefox. But it is again reproducible in firefox 11.
Refer 


Actual results:

Firefox frame does not take the state "active" when it is the activated frame.



Expected results:

Firefox frame should take the state "active" when it is the activated frame.
(Reporter)

Updated

6 years ago
Keywords: regression

Comment 1

6 years ago
Can anybody confirm? Original patch from bug 566542 is covered by automated testing.

Updated

6 years ago
Summary: Frame for firefox does not implement the state "active" when firefox is the active frame → Frame for firefox does not implement the state "active" when firefox is the active frame (bug 566542 reincarnation)
(In reply to alexander :surkov from comment #1)
> Can anybody confirm? Original patch from bug 566542 is covered by automated
> testing.

I'm not sure what we mean "frame" here do we mean the application accessible, the forground  root accessible or document or something else?

Comment 3

6 years ago
I think the foreground root accessible
(Reporter)

Comment 4

6 years ago
Refer https://bugzilla.mozilla.org/show_bug.cgi?id=566542 for a screenshot.

Comment 5

6 years ago
I can reproduce the problem in ubuntu10.40, Nightly14.0a1.
Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120322 Firefox/14.0a1 ID:20120322031220


And I can reproduce on local build(non PGO) with following .mozconfig.
mk_add_options MOZ_CO_PROJECT=browser
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/firefox-build
ac_add_options --enable-application=browser

However, I can not reproduce on local build(non PGO) with following .mozconfig. It works as expected.
mk_add_options MOZ_CO_PROJECT=browser
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/firefox-build
ac_add_options --enable-application=browser
ac_add_options --disable-accessibility


So, something wrong(broken) in mozilla build system...?

Comment 6

6 years ago
(In reply to Alice0775 White from comment #5)

> However, I can not reproduce on local build(non PGO) with following
> .mozconfig. It works as expected.
> mk_add_options MOZ_CO_PROJECT=browser
> mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/firefox-build
> ac_add_options --enable-application=browser
> ac_add_options --disable-accessibility
> 
> 
> So, something wrong(broken) in mozilla build system...?

Having --disable-accessibility option you shouldn't have accessibility at all.
You need to log in before you can comment on or make changes to this bug.