Time Picker behaves erractically when min and max is set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-ui-toolkit (Ubuntu) |
Confirmed
|
High
|
Zsombor Egri |
Bug Description
Using this example qml,
import QtQuick 2.0
import Ubuntu.Components 1.1
import Ubuntu.
MainView {
width: units.gu(48)
height: units.gu(60)
Column {
DatePicker {
id: datePicker
mode: 'Years|Months|Days'
var d = new Date()
}
var d = new Date()
}
date: {
var d = new Date()
}
}
DatePicker {
id: timePicker
mode: 'Hours|
var d = new Date()
}
var d = new Date()
}
date: {
var d = new Date()
}
}
}
}
The timepicker behaves erractically. When selecting a minute, the hour picker. When selecting things with the second picker, both the hour and minute pickers advance forward as well.
It's interesting the min and max dates are being set (this was discovered trying to workaround bug https:/
Changed in ubuntu-ui-toolkit: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Zsombor Egri (zsombi) |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
assignee: | nobody → Zsombor Egri (zsombi) |
importance: | Undecided → High |
status: | New → Confirmed |
no longer affects: | ubuntu-ui-toolkit |
Let's please expand the pickers testcases to include a regression test for this so we don't regress on it in the future. It would be trivial to add.