touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #115183
[Bug 1511839] Re: On dynamically created pages, head.sections.selectedIndex can't be set to -1
Raised to critical as blocks migration to 1.3.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: Zoltan Balogh (bzoltan) => Zsombor Egri (zsombi)
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1511839
Title:
On dynamically created pages, head.sections.selectedIndex can't be set
to -1
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
Ubuntu.Components version: 1.3
Some times it is desirable that none of the entries in the head.sections.model is selected by default.
While that works fine on statically created pages, if I define a page inside a component, or load it directly from a QML file, this is not respected.
The following sample QML application reproduces the problem:
import QtQuick 2.3
import Ubuntu.Components 1.3
MainView {
width: units.gu(30)
height: units.gu(60)
Component {
id: pageComponent
Page {
id: page
title: i18n.tr("The Page")
head.sections.model: ["one","two","three"]
head.sections.selectedIndex: -1
}
}
PageStack {
id: stack
}
Component.onCompleted: {
stack.push(pageComponent)
}
}
Expected result: a page with no section selected.
What happens: the first section of the header is selected by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511839/+subscriptions
References