Bug 516721

Summary:	MonthCalendar: all widgets have implemented the same position and size as whole TreeTable
Product:	[Mono] UI Automation	Reporter:	calen chen <cachen>
Component:	Winforms - General	Assignee:	E-mail List <mono-a11y-bugs>
Status:	NEW ---	QA Contact:	E-mail List <mono-a11y-qa>
Severity:	Normal
Priority:	P3 - Medium
Version:	Release 1.0
Target Milestone:	---
Hardware:	x86
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description calen chen 2009-06-26 07:51:04 UTC

REPRO:

1. run uia2atk/test/samples/monthcalendar.py
2. run accerciser, expand filler, browse to the "table column header" or "table cells", a red rectangle appeared on UI
3. see each accessible's postion and size on interface viewer under Component tree

RESULTS:

all table column headers and table cells have the same position and size as TreeTable. and red rectangle of each accessible is browse to TreeTable

EXPECTED RESULTS:

each accessible should have their own position differently

Comment 1 Rui Guo 2009-07-07 03:28:32 UTC

I think it's difficult for us to get the bound of a child control of a MonthCalendar without make big modification in SWF.

Root Cause:
The drawing of MonthCalendar is handled by the Theme class. Usually our MonthCalendar is drawn by SWF/ThemeWin32Classic.cs.DrawMonthCalendar(), though several internal members of the MonthCalendar control such as "mc.calendar_spacing", "mc.date_cell_size", "mc.SingleMonthSize" and "mc.CalendarDimensions" are used in the rendering, the final bound of each child control is still controlled by the specific theme engine logic. So IMO we cannot perfectly fix this bug unless expose a bunch of interfaces and enable the theme engine to tell uia the bound of each child control drawn by the engine.

Comment 2 Rui Guo 2009-07-07 10:17:41 UTC

Maybe that's not so difficult, since we could just copy the bound calculation logics from SWF/MonthCalendar.HitTest.