A11y should use nsImageMapUtils::FindImageMap to find image maps, to avoid duplicating code. Fix attached.

Comment on attachment 437524 [details] [diff] [review] Fix r=me, thanks

landed on 1.9.3 0 - http://hg.mozilla.org/mozilla-central/rev/e88d2327e25d

backed out - http://hg.mozilla.org/mozilla-central/rev/85454945336e Thunderbird compilation errors (http://tinderbox.mozilla.org/showlog.cgi?log=Thunderbird/1270732140.1270733069.6613.gz): ../src/base/libaccessibility_base_s.a(nsAccessibilityService.o): In function `nsAccessibilityService::CreateHTMLImageAccessible(nsIFrame*, nsIAccessible**)': /buildbot/comm-central-trunk-bloat-linux/build/mozilla/accessible/src/base/nsAccessibilityService.cpp:663: undefined reference to `nsImageMapUtils::FindImageMap(nsIDocument*, nsAString_internal const&)' /usr/bin/ld: libaccessibility.so: hidden symbol `nsImageMapUtils::FindImageMap(nsIDocument*, nsAString_internal const&)' isn't defined /usr/bin/ld: final link failed: Nonrepresentable section on output

I think the bustage would affect any non-shared, non-libxul build. I think the issue is the nsImageMapUtils::FindImageMap obviously has hidden visibility. For libxul and static builds this doesn't matter because accessibility gets linked in with content and layout into one big shared library. For non-libxul builds (which afaik FF developers still frequently use as well as TB tinderboxes) accessibility is a different shared library, and hence can't access the hidden function.

Isn't this still going to break non-libxul builds?

Do we need a FindImageMapExternal here?

(In reply to comment #5) > Isn't this still going to break non-libxul builds? Yes, hence the dependency on the bug to kill --disable-libxul. Maybe I should have used [waiting for branch] instead...

Ms2ger, the patch in comment 8 doesn't seem to apply to m-c...

Did it have bug 581644 at that point?

Hmm. Probably not. I'll try again tonight.

Ugh. I missed the fact that this last attachment had a checkin comment but no From line. Sorry about that.... :(