Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 425373

Summary:	Windows automation framework "XAML" - support control "Page"
Product:	[Technology] Jubula	Reporter:	Markus Tiede <markus.tiede>
Component:	RC	Assignee:	Project Inbox <jubula.rc-inbox>
Status:	CLOSED FIXED	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	enhancement
Priority:	P2	CC:	alexandra.schladebeck, sebastian.jubula
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows All
Whiteboard:
Bug Depends on:
Bug Blocks:	425256, 426981

Description Markus Tiede

2014-01-10 08:52:30 EST

We should add support for "Page"-controls.

Comment 1 Alexandra Schladebeck

2014-01-13 04:51:37 EST

As far as I understand, this is a container component. Since we don't support whole screens / pages on other toolkits (except in an "application" context), I'm marking this as wontfix. 

If anyone has other information or arguments, please reopen.

Comment 2 Oliver Goetz

2014-01-14 10:00:53 EST

Closed due to comment 1

Comment 3 Markus Tiede

2014-01-30 05:56:20 EST

Re-opening (as we need implicit support for this) and setting the dependency as mentioned in comment 1.

Comment 4 Sebastian Struckmann

2014-02-10 01:04:01 EST

We support this component. I checked the object mapping and executed a small test on some buttons inside this container successfully.

Comment 5 Oliver Goetz

2014-02-12 09:50:41 EST

Verified, I was able to map the components included in the Page container and was able to perform clicks on them.