[Touch-packages] [Bug 1671121] Re: Deleting something from the history view breaks scrolling and the ability to click on some things

[Zsombor Egri]

I explained 2) badly :) I was about to mean that use other component for
delegate and put a button on it, so when you click it that button
deletes the delegate. Just to rule out the ListItem itself. But the 1)
already rules it out, so it is indeed the popover which does something
bad. And probably it is related to the focus handling, as I do not see
anything else the popover would affect the ListView functionalities.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1671121

Title:
  Deleting something from the history view breaks scrolling and the
  ability to click on some things

Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  What happened:
  1) Launch the webbrowser-app
  2) Go to the history view
  3) Scroll up/down and notice that the scrolling works
  4) Right-click delete the first entry
  5) Try to scroll up/down and notice that the scrolling doesn't work, notice 
you can't click on history entries, but you can select back in the header. 
Notice then you can't scroll the webviews or select any of the tabs.

  What I expected to happen:
  After step #4 for the scrolling/click focus to still function.


  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Xenial + overlay

  $ apt-cache policy webbrowser-app liboxideqt-qmlplugin 
  webbrowser-app:
Installed: 0.23+16.04.20170125.1-0ubuntu1
Candidate: 0.23+16.04.20170125.1-0ubuntu1
Version table:
   *** 0.23+16.04.20170125.1-0ubuntu1 500
  500 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   0.23+16.04.20161028-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   0.23+16.04.20160413-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  liboxideqt-qmlplugin:
Installed: 1.20.4-0ubuntu0.16.04.1+overlay1
Candidate: 1.20.4-0ubuntu0.16.04.1+overlay1
Version table:
   *** 1.20.4-0ubuntu0.16.04.1+overlay1 500
  500 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   1.20.4-0ubuntu0.16.04.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.13.6-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1671121/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1671121] Re: Deleting something from the history view breaks scrolling and the ability to click on some things

[Zsombor Egri]

Let's try to rule out few things:
1) try to use the ListItem action to delete it
2) try to use a different delegate to delete the item.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1671121

Title:
  Deleting something from the history view breaks scrolling and the
  ability to click on some things

Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  What happened:
  1) Launch the webbrowser-app
  2) Go to the history view
  3) Scroll up/down and notice that the scrolling works
  4) Right-click delete the first entry
  5) Try to scroll up/down and notice that the scrolling doesn't work, notice 
you can't click on history entries, but you can select back in the header. 
Notice then you can't scroll the webviews or select any of the tabs.

  What I expected to happen:
  After step #4 for the scrolling/click focus to still function.


  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Xenial + overlay

  $ apt-cache policy webbrowser-app liboxideqt-qmlplugin 
  webbrowser-app:
Installed: 0.23+16.04.20170125.1-0ubuntu1
Candidate: 0.23+16.04.20170125.1-0ubuntu1
Version table:
   *** 0.23+16.04.20170125.1-0ubuntu1 500
  500 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   0.23+16.04.20161028-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   0.23+16.04.20160413-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  liboxideqt-qmlplugin:
Installed: 1.20.4-0ubuntu0.16.04.1+overlay1
Candidate: 1.20.4-0ubuntu0.16.04.1+overlay1
Version table:
   *** 1.20.4-0ubuntu0.16.04.1+overlay1 500
  500 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   1.20.4-0ubuntu0.16.04.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.13.6-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1671121/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1642617] Re: UITK FTBFS on Qt 5.7.1

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1642617

Title:
  UITK FTBFS on Qt 5.7.1

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  
https://launchpadlibrarian.net/293820525/buildlog_ubuntu-zesty-amd64.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5build1~1_BUILDING.txt.gz
  ---
  cc1plus: all warnings being treated as errors
  Makefile:1005: recipe for target '.obj/header_ubuntutoolkitmodule.o' failed
  make[3]: *** [.obj/header_ubuntutoolkitmodule.o] Error 1
  ---

  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642617/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1618007] Re: Invalid property assignment in ActivityIndicatorStyle.qml

[Zsombor Egri]

This should have been landed already...

-- 
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/1618007

Title:
  Invalid property assignment in ActivityIndicatorStyle.qml

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  I get

  file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618007/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1624331] Re: tst_listitem_focus.13.qml unit test failure

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

-- 
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/1624331

Title:
  tst_listitem_focus.13.qml unit test failure

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  FAIL!  : 
components::ListItemFocus::test_refocus_listview_on_last_focused_item(No 
content) 'Focus frame shown for the item' returned FALSE. ()
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_listitem_focus.13.qml(504)]

  
  See 
https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624331/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1628855] Re: UITK Gallery: first click on left panel list items activates the focus frame

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1628855

Title:
  UITK Gallery: first click on left panel list items activates the focus
  frame

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  ubuntu-ui-toolkit/staging r2133

  Environment:
  Yakkety Beta
  libqt5core5a:
Installed: 5.6.1+dfsg-3ubuntu5~xenialoverlay1~1

  How to reproduce:
  - build uitk source
  - run the gallery (./gallery.sh)
  - Click on a list item in the left panel

  Expected outcome:
  the list item is selected, no focus frame is shown

  Actual outcome:
  The list item is selected and the focus frame is shown around it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628855/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1624343] Re: Qt5.6: UbuntuListView unit test fails with TypeError

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1624343

Title:
  Qt5.6: UbuntuListView unit test fails with TypeError

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Failing unit tests with Qt 5.6:

  * Start testing of components *
  Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.4.0 20160609)
  PASS   : components::UbuntuListView::initTestCase()
  PASS   : components::UbuntuListView::test_collapseByClickingOutside()
  PASS   : components::UbuntuListView::test_collapseOnClick()
  PASS   : components::UbuntuListView::test_destroyAndRecreateExpanded()
  PASS   : components::UbuntuListView::test_dimOthers()
  PASS   : components::UbuntuListView::test_expandedItem()
  FAIL!  : components::UbuntuListView::test_noScrollingNeeded() Uncaught 
exception: Type error
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(116)]
  FAIL!  : components::UbuntuListView::test_scrollIntoView() Uncaught 
exception: Type error
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(142)]
  FAIL!  : components::UbuntuListView::test_scrollToTop() Uncaught exception: 
Type error
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(129)]
  PASS   : components::UbuntuListView::cleanupTestCase()
  Totals: 7 passed, 3 failed, 0 skipped, 0 blacklisted
  * Finished testing of components *

  See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/1201/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624343/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1580172] Re: Enable UITK arm64 unit tests

[Zsombor Egri]

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

-- 
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/1580172

Title:
  Enable UITK arm64 unit tests

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Trying to enable unit tests on xenial arm64, I get the following
  problems:

  ---
  9 failures which MUST be fixed:
    tst_pagehead_visible.qml
    tst_picker.qml
    tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml
    tst_tabs_with_repeater.qml
    tst_textinput_touch.qml
  ---

  Full build log at https://launchpadlibrarian.net/258791309
  /buildlog_ubuntu-xenial-arm64.ubuntu-ui-
  toolkit_1.3.1960+16.04.20160502+arm64~1_BUILDING.txt.gz

  arm64 builds are fine from UITK perspective, but as arm64 is started
  to be used we should be executing and passing the tests too.

  https://code.launchpad.net/~timo-jyrinki/ubuntu-ui-
  toolkit/enable_arm64_unittests/+merge/292144 can't go in before these
  are fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580172/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1624328] Re: tst_listitem failures

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

-- 
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/1624328

Title:
  tst_listitem failures

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Must be fixed for Qt 5.6.

  FAIL!  : components::ListItemAPI::test_0_defaults() 
theme.palette.selected.background color by default
  FAIL!  : components::ListItem13API::test_0_defaults() 
theme.palette.selected.background color by default

  
  See 
https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624328/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1580172] Re: Enable UITK arm64 unit tests

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1580172

Title:
  Enable UITK arm64 unit tests

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Trying to enable unit tests on xenial arm64, I get the following
  problems:

  ---
  9 failures which MUST be fixed:
    tst_pagehead_visible.qml
    tst_picker.qml
    tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml
    tst_tabs_with_repeater.qml
    tst_textinput_touch.qml
  ---

  Full build log at https://launchpadlibrarian.net/258791309
  /buildlog_ubuntu-xenial-arm64.ubuntu-ui-
  toolkit_1.3.1960+16.04.20160502+arm64~1_BUILDING.txt.gz

  arm64 builds are fine from UITK perspective, but as arm64 is started
  to be used we should be executing and passing the tests too.

  https://code.launchpad.net/~timo-jyrinki/ubuntu-ui-
  toolkit/enable_arm64_unittests/+merge/292144 can't go in before these
  are fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580172/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1611327] Re: Disabled ListItem inside ListView takes focus but does not show focus ring

[Zsombor Egri]

** Description changed:

  Items outside of a ListView are skipped when using keyboard navigation
  to change the focus. However, a ListItem inside a ListView takes the
  focus even when it is disabled, but it does not show the focus frame
  when focused.
  
  For example, execute this QML program:
  
  import QtQuick 2.4
  import Ubuntu.Components 1.3
  
  Item {
  width: units.gu(50)
  height: units.gu(50)
  
- ListView {
+ UbuntuListView {
  anchors.fill: parent
  delegate: ListItem {
  enabled: index != 2
  Label {
  anchors.centerIn: parent
  text: parent.enabled ? "enabled" : "disabled"
  }
  }
  model: 5
  }
  }
  
  Press TAB to focus on the ListView. Then press the down-cursor-key twice
  to move the focus down inside the ListView. The focus will be on the
  disabled item, but not focus frame is visible This is confusing for the
  user since the focus seems to disappear, and the Item where the focus
  seems to be (although invisible) cannot be triggered because it is
  disabled.
  
  Note: When fixing this bug, also test the solution for Horizontal
  ListViews (and RightToLeft and BottomToTop directions), since I
  encountered this bug in the scrolling toolbar (in progress) that has a
  Horizontal, RightToLeft ListView.
  
  ==UX Fix===
  
  Bypass focus for a disabled item and show focus immediately for the next
  available enabled item.

-- 
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/1611327

Title:
  Disabled ListItem inside ListView takes focus but does not show focus
  ring

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Items outside of a ListView are skipped when using keyboard navigation
  to change the focus. However, a ListItem inside a ListView takes the
  focus even when it is disabled, but it does not show the focus frame
  when focused.

  For example, execute this QML program:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  UbuntuListView {
  anchors.fill: parent
  delegate: ListItem {
  enabled: index != 2
  Label {
  anchors.centerIn: parent
  text: parent.enabled ? "enabled" : "disabled"
  }
  }
  model: 5
  }
  }

  Press TAB to focus on the ListView. Then press the down-cursor-key
  twice to move the focus down inside the ListView. The focus will be on
  the disabled item, but not focus frame is visible This is confusing
  for the user since the focus seems to disappear, and the Item where
  the focus seems to be (although invisible) cannot be triggered because
  it is disabled.

  Note: When fixing this bug, also test the solution for Horizontal
  ListViews (and RightToLeft and BottomToTop directions), since I
  encountered this bug in the scrolling toolbar (in progress) that has a
  Horizontal, RightToLeft ListView.

  ==UX Fix===

  Bypass focus for a disabled item and show focus immediately for the
  next available enabled item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1611327/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1627078] Re: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property

[Zsombor Egri]

For teh sake of QQC2 compatibility, let's call the property 'pressed'.
Scrollbars are exposed by ScrollView, so there's no need to expose there
anything.

-- 
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/1627078

Title:
  ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  I'm trying to implement a "page indicator" to be shown when the user
  scrolls a Flickable using a UITK ScrollBar. The idea is to mimic a
  feature available in Adobe Reader for Android.

  i.e. http://imgur.com/a/OzjYG

  In order to do this, I have to access the "draggingThumb" property of
  the style instance of a UITK ScrollBar, which is meant to be private.

  Item {
  [...]
  visible: scrollView.verticalScrollbar.__styleInstance.draggingThumb
  }

  What it could be useful is to expose this property directly in the ScrollBar.
  Using the Flickable properties for this purpose would be a bit complicated, 
since it wouldn't be desiderable to see such overlay during an "ordinary" 
touch/flick event.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1627078/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1618007] Re: Invalid property assignment in ActivityIndicatorStyle.qml

[Zsombor Egri]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

-- 
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/1618007

Title:
  Invalid property assignment in ActivityIndicatorStyle.qml

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  I get

  file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618007/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError

[Zsombor Egri]

If the primaryPageSource is a component, the APL works fine.

This problem doesn't appear to affect adding pages to columns

-- 
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/1585996

Title:
  UITK gallery: can't open subpages on Qt 5.6 because of TypeError

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery
  (installed from Store). In logs I have:

  qml: sourcePage must be added to the view to add new page.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585996/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError

[Zsombor Egri]

There are two problems:
1) the component the APL creates the default metrics is called in parallel by 
two changes: body.onChildrenChanged is processed in parallel with 
d.onDefaultColumnWidthChanged, both call the object creation. This can be 
filtered out, as done in the attached branch.

2) variant type properties are causing trouble when a string value is
added. The property change signal is triggered twice, which - in case of
the primaryPageSource - causes the primary page to be loaded twice.
Changing the property type to string makes APL to work again. With the
previous change applied too.

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/fixAplHickupQt56

-- 
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/1585996

Title:
  UITK gallery: can't open subpages on Qt 5.6 because of TypeError

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery
  (installed from Store). In logs I have:

  qml: sourcePage must be added to the view to add new page.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585996/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1585996

Title:
  UITK gallery: can't open subpages on Qt 5.6 because of TypeError

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery
  (installed from Store). In logs I have:

  qml: sourcePage must be added to the view to add new page.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585996/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Critical => High

-- 
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/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in qtsystems-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError

[Zsombor Egri]

** 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/1585996

Title:
  UITK gallery: can't open subpages on Qt 5.6 because of TypeError

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery
  (installed from Store). In logs I have:

  qml: sourcePage must be added to the view to add new page.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585996/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1624328] Re: tst_listitem failures

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** 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/1624328

Title:
  tst_listitem failures

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Must be fixed for Qt 5.6.

  FAIL!  : components::ListItemAPI::test_0_defaults() 
theme.palette.selected.background color by default
  FAIL!  : components::ListItem13API::test_0_defaults() 
theme.palette.selected.background color by default

  
  See 
https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624328/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622577] Re: tst_pagestack_deprecated_toolbar unit test warnings with qt56

[Zsombor Egri]

** 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/1622577

Title:
  tst_pagestack_deprecated_toolbar unit test warnings with qt56

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  ubuntu@xenial1:~/dev/ubuntu-ui-toolkit/staging/tests/unit/components$ 
qmltestrunner -import ../../../qml/ -input tst_pagestack_deprecated_toolbar.qml 
  qml: Page.tools is a deprecated property. Please use Page.head instead.
  qml: Page.tools is a deprecated property. Please use Page.head instead.
  qml: WARNING! Do not put Page/Tabs/PageStack inside another Page because that 
causes confusion which is the active page that sets the title and actions.
  qml: WARNING! Do not put Page/Tabs/PageStack inside another Page because that 
causes confusion which is the active page that sets the title and actions.
  * Start testing of qmltestrunner *
  Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.4.0 20160609)
  PASS   : qmltestrunner::PageStackAPI::initTestCase()
  PASS   : qmltestrunner::PageStackAPI::test_active_bug1260116()
  QDEBUG : qmltestrunner::PageStackAPI::test_active_bug1260116() qml: 
Page.tools is a deprecated property. Please use Page.head instead.
  PASS   : qmltestrunner::PageStackAPI::test_currentPage()
  PASS   : qmltestrunner::PageStackAPI::test_depth()
  PASS   : qmltestrunner::PageStackAPI::test_pop_to_tabs_bug1316736()
  PASS   : qmltestrunner::PageStackAPI::test_tabs_inside_stack_bug1187850()
  PASS   : qmltestrunner::PageStackAPI::test_title_bug1143345_bug1317902()
  PASS   : qmltestrunner::PageStackAPI::test_tools_bug1126197()
  QDEBUG : qmltestrunner::PageStackAPI::test_tools_bug1126197() qml: Page.tools 
is a deprecated property. Please use Page.head instead.
  PASS   : qmltestrunner::PageStackAPI::cleanupTestCase()
  QWARN  : qmltestrunner::UnknownTestFunc() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144:
 TypeError: Cannot read property 'count' of null
  QWARN  : qmltestrunner::UnknownTestFunc() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144:
 TypeError: Cannot read property 'count' of null
  QWARN  : qmltestrunner::UnknownTestFunc() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144:
 TypeError: Cannot read property 'count' of null
  QWARN  : qmltestrunner::UnknownTestFunc() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144:
 TypeError: Cannot read property 'count' of null
  QWARN  : qmltestrunner::UnknownTestFunc() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144:
 TypeError: Cannot read property 'count' of null
  QWARN  : qmltestrunner::UnknownTestFunc() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144:
 TypeError: Cannot read property 'count' of null
  Totals: 9 passed, 0 failed, 0 skipped, 0 blacklisted
  * Finished testing of qmltestrunner *

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1622577/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial

[Zsombor Egri]

** 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/1586013

Title:
  UITK Date picker broken on xenial

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6
  (right).

  More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting

  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml
  [...]
  FAIL!  : components::DatePicker13API::test_1_changeMinimumBeforeDate() 
Uncaught exception: Cannot call method hasOwnProperty of null
   Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1624340] Re: tst_textfield.11.qml unit test failures

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => 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/1624340

Title:
  tst_textfield.11.qml unit test failures

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Fails with Qt 5.6.

  FAIL!  : components::TextFieldAPI::test_0_cursorRectangle() cursorRectangle 0 
by default
 Actual   (): QRectF(0, 4, 1, 16)
 Expected (): QRectF(0, 0, 0, 0)
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textfield.11.qml(168)]

  See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/1201/consoleFull.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624340/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1624331] Re: tst_listitem_focus.13.qml unit test failure

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** 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/1624331

Title:
  tst_listitem_focus.13.qml unit test failure

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  FAIL!  : 
components::ListItemFocus::test_refocus_listview_on_last_focused_item(No 
content) 'Focus frame shown for the item' returned FALSE. ()
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_listitem_focus.13.qml(504)]

  
  See 
https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624331/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1616858] Re: ActionBar overflow issues with Qt 5.6

[Zsombor Egri]

** 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/1616858

Title:
  ActionBar overflow issues with Qt 5.6

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  With Qt 5.6 I'm seeing problems with the ActionBar.

  1. tst_actionbar.13.qml passes but there's lots of warnings:

  QWARN  :
  components::ActionBarApi::test_number_of_actions_in_overflow()
  ./_build/qml/Ubuntu/Components/Themes/Ambiance/1.3/OverflowPanel.qml:66:
  ReferenceError: modelData is not defined

  The unit test should be failing. And obviously there's a bug here.

  2. Running tst_actionbar.13.qml in the launcher the overflow button is
  absent.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1616858/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1625137] Re: Layouts unit tests fail on Yakkety

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => 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/1625137

Title:
  Layouts unit tests fail on Yakkety

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/checkresults.sh 
/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/*.xml || exit 1; 
pep8 /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2 || exit 1;
  3 fatal warnings which MUST be fixed:
layouts


  Only warnings, but our shell script checks for warnings and makes them
  fatal.


  * Start testing of tst_Layouts *
  Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 6.2.0 20160914)
  PASS   : tst_Layouts::initTestCase()
  [New Thread 0x7fffe1824700 (LWP 19588)]
  [New Thread 0x7fffe1023700 (LWP 19589)]
  [New Thread 0x7fffe0822700 (LWP 19590)]
  [New Thread 0x7fffe0021700 (LWP 19591)]
  [New Thread 0x7fffdf820700 (LWP 19592)]
  [Thread 0x7fffdf820700 (LWP 19592) exited]
  PASS   : tst_Layouts::testCase_NoLayouts()
  [New Thread 0x7fffdf820700 (LWP 19593)]
  [Thread 0x7fffdf820700 (LWP 19593) exited]
  PASS   : tst_Layouts::testCase_SimpleLayout()
  [New Thread 0x7fffdf820700 (LWP 19594)]
  [Thread 0x7fffdf820700 (LWP 19594) exited]
  PASS   : tst_Layouts::testCase_SimpleLayout_Medium()
  [New Thread 0x7fffdf820700 (LWP 19595)]
  [Thread 0x7fffdf820700 (LWP 19595) exited]
  PASS   : tst_Layouts::testCase_SimpleLayout_Large()
  [New Thread 0x7fffdf820700 (LWP 19596)]
  [Thread 0x7fffdf820700 (LWP 19596) exited]
  PASS   : tst_Layouts::testCase_OverlappingCondition()
  [New Thread 0x7fffdf820700 (LWP 19597)]
  [Thread 0x7fffdf820700 (LWP 19597) exited]
  PASS   : tst_Layouts::testCase_ExternalLayouts()
  [New Thread 0x7fffdf820700 (LWP 19598)]
  [Thread 0x7fffdf820700 (LWP 19598) exited]
  PASS   : tst_Layouts::testCase_ExternalLayouts_Medium()
  [New Thread 0x7fffdf820700 (LWP 19599)]
  [Thread 0x7fffdf820700 (LWP 19599) exited]
  PASS   : tst_Layouts::testCase_ExternalLayouts_Large()
  [New Thread 0x7fffdf820700 (LWP 19600)]
  [Thread 0x7fffdf820700 (LWP 19600) exited]
  PASS   : tst_Layouts::testCase_NestedLayouts()
  [New Thread 0x7fffdf820700 (LWP 19601)]
  [Thread 0x7fffdf820700 (LWP 19601) exited]
  PASS   : tst_Layouts::testCase_NestedLayouts_ExtraLarge()
  [New Thread 0x7fffdf820700 (LWP 19602)]
  [Thread 0x7fffdf820700 (LWP 19602) exited]
  PASS   : tst_Layouts::testCase_ResizingContainers()
  [New Thread 0x7fffdf820700 (LWP 19603)]
  XFAIL  : tst_Layouts::testCase_CurrentLayoutChange() Layout change should not 
happen when component is not defined
 Loc: [tst_layouts.cpp(387)]
  [Thread 0x7fffdf820700 (LWP 19603) exited]
  PASS   : tst_Layouts::testCase_CurrentLayoutChange()
  [New Thread 0x7fffdf820700 (LWP 19604)]
  XFAIL  : tst_Layouts::testCase_PositioningOnLayoutChange() Layout change 
should not happen when component is not defined
 Loc: [tst_layouts.cpp(408)]
  [Thread 0x7fffdf820700 (LWP 19604) exited]
  PASS   : tst_Layouts::testCase_PositioningOnLayoutChange()
  [New Thread 0x7fffdf820700 (LWP 19605)]
  [Thread 0x7fffdf820700 (LWP 19605) exited]
  PASS   : tst_Layouts::testCase_LaidOutItemsOutsideOfLayout()
  [New Thread 0x7fffdf820700 (LWP 19606)]
  [Thread 0x7fffdf820700 (LWP 19606) exited]
  PASS   : tst_Layouts::testCase_OverlaidInItemLayout()
  [New Thread 0x7fffdf820700 (LWP 19607)]
  [Thread 0x7fffdf820700 (LWP 19607) exited]
  PASS   : tst_Layouts::testCase_AnchorFilledReparenting()
  [New Thread 0x7fffdf820700 (LWP 19608)]
  [Thread 0x7fffdf820700 (LWP 19608) exited]
  PASS   : tst_Layouts::testCase_AnchorFilledMargins()
  [New Thread 0x7fffdf820700 (LWP 19609)]
  [Thread 0x7fffdf820700 (LWP 19609) exited]
  PASS   : tst_Layouts::testCase_AnchorFilledSeparateMargins()
  [New Thread 0x7fffdf820700 (LWP 19610)]
  [Thread 0x7fffdf820700 (LWP 19610) exited]
  PASS   : tst_Layouts::testCase_AnchorCenteredInDefault()
  [New Thread 0x7fffdf820700 (LWP 19611)]
  [Thread 0x7fffdf820700 (LWP 19611) exited]
  PASS   : tst_Layouts::testCase_AnchorVerticalCenter()
  [New Thread 0x7fffdf820700 (LWP 19612)]
  [Thread 0x7fffdf820700 (LWP 19612) exited]
  PASS   : tst_Layouts::testCase_AnchorVerticalCenterOffset()
  [New Thread 0x7fffdf820700 (LWP 19613)]
  [Thread 0x7fffdf820700 (LWP 19613) exited]
  PASS   : tst_Layouts::testCase_AnchorHorizontalCenter()
  [New Thread 0x7fffdf820700 (LWP 19614)]
  [Thread 0x7fffdf820700 (LWP 19614) exited]
  PASS   : tst_Layouts::testCase_AnchorHorizontalCenterOffset()
  [New Thread 0x7fffdf820700 (LWP 19615)]
  [Thread 0x7fffdf820700 (LWP 19615) exited]
  PASS   : tst_Layouts::testCase_AnchorCenterWithOffset()
  [New Thread 0x7fffdf820700 (LWP 19616)]
  [Thread 0x7fffdf820700 (LWP 19616) exited]
  PASS   : 

[Touch-packages] [Bug 1624342] Re: tst_textarea.11.qml unit test fails

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => 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/1624342

Title:
  tst_textarea.11.qml unit test fails

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Fails with Qt 5.6.

  FAIL!  : components::TextAreaAPI::test_0_color() TextArea.color is same as 
TextEdit.canUndo
 Actual   (): #5d5d5d
 Expected (): #00
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)]

  See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/1201/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624342/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1461571] Re: Text field clear button does not work with first predicted word

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1461571

Title:
  Text field clear button does not work with first predicted word

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-touch/rc-proposed/bq-aquaris.en-proposed #219

  When entering text into a text field using OSK with predictive text
  enabled, it is not possible to clear the first word using the clear
  button.

  Steps:
  1) Load Ubuntu UI Toolkit Gallery
  2) Select Text Field -> Standard
  3) Type in a few characters using the OSK, so that the word in text field 
remains underlined and suggestions are displayed by OSK.
  4) Press clear button in the text field.

  Expected result:
  The text in the text field should be cleared.

  Actual result:
  The clear button does not work and the text remains.

  
  Note that if there are multiple words entered then the clear button will work 
as expected. This problem only happens if there is only 1 word that is being 
deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1461571/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1587580] Re: No way to escape an ampersand in UCAction

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1587580

Title:
  No way to escape an ampersand in UCAction

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Let's say we have an Ubuntu.Action as follow:

  import Ubuntu.Components 1.3 as Ubuntu
  Ubuntu.Action {
  text: "Apps & Scopes"
  }

  UCAction translates the ampersand as a mnemonic, using QKeySequence.
  A way to escape a mnemonic in Qt is to add another ampersand. The resulting 
string is "Apps && Scopes".

  The UITK component seems not to take in account this situation, since:

  - How the string should be shown in e.g. an ActionBar:
  "Apps & Scopes"

  - How the string is displayed instead in an ActionBar:
  "Apps && Scopes"

  QKeySequence returns no mnemonic as expected, but UCAction shows two
  ampersands.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1587580/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1623841] Re: ActionSelectionPopover broken in latest UITK release

[Zsombor Egri]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/fixActionListTrunk

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1623841

Title:
  ActionSelectionPopover broken in latest UITK release

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  I upgraded packages on my laptop today (xenial + stable overlay PPA)
  and builds of lp:webbrowser-app started failing in tst_QmlTests.

  Those are the failures I’m seeing:

  FAIL!  : QmlTests::NewTabView::test_delete_top_site() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)]
  FAIL!  : QmlTests::NewTabView::test_expand_bookmarks() 'verify()' returned 
FALSE. ()
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(82)]
  FAIL!  : QmlTests::NewTabView::test_keyboard_navigation() 'verify()' returned 
FALSE. ()
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(82)]
  FAIL!  : QmlTests::NewTabView::test_keyboard_navigation() 'verify()' returned 
FALSE. ()
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(189)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_close() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_new_tab() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_reload() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)]
  FAIL!  : QmlTests::TabsBar::test_menu_states_on_new_tab() Uncaught exception: 
Cannot read property 'enabled' of null
 Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_TabsBar.qml(245)]
  FAIL!  : QmlTests::TabsBar::test_menu_states_on_page() Uncaught exception: 
Cannot read property 'enabled' of null
 Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_TabsBar.qml(256)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1623841/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622742] Re: ActivityIndicator broken, likely due to Qt 5.6 update

[Zsombor Egri]

Could you check whether staging gives you better result? The branch from
Florian is under landing currently...

-- 
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/1622742

Title:
  ActivityIndicator broken, likely due to Qt 5.6 update

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  QML ActivityIndicator: file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

  The indicator isn't displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 
1.3.2073+16.04.20160824build1~~xenialoverlay1~1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 12 22:31:21 2016
  InstallationDate: Installed on 2016-05-06 (128 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1622742/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1623841] Re: ActionSelectionPopover broken in latest UITK release

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1623841

Title:
  ActionSelectionPopover broken in latest UITK release

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  I upgraded packages on my laptop today (xenial + stable overlay PPA)
  and builds of lp:webbrowser-app started failing in tst_QmlTests.

  Those are the failures I’m seeing:

  FAIL!  : QmlTests::NewTabView::test_delete_top_site() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)]
  FAIL!  : QmlTests::NewTabView::test_expand_bookmarks() 'verify()' returned 
FALSE. ()
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(82)]
  FAIL!  : QmlTests::NewTabView::test_keyboard_navigation() 'verify()' returned 
FALSE. ()
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(82)]
  FAIL!  : QmlTests::NewTabView::test_keyboard_navigation() 'verify()' returned 
FALSE. ()
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(189)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_close() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_new_tab() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_reload() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)]
  FAIL!  : QmlTests::TabsBar::test_menu_states_on_new_tab() Uncaught exception: 
Cannot read property 'enabled' of null
 Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_TabsBar.qml(245)]
  FAIL!  : QmlTests::TabsBar::test_menu_states_on_page() Uncaught exception: 
Cannot read property 'enabled' of null
 Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_TabsBar.qml(256)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1623841/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1590005] Re: Focus can go be moved inside ListItem in a horizontal ListView

[Zsombor Egri]

** Branch unlinked: lp:~zsombi/ubuntu-ui-toolkit/dontFocusDisabledLi

-- 
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/1590005

Title:
  Focus can go be moved inside ListItem in a horizontal ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Run this code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  model: 10
  orientation: ListView.Horizontal
  delegate: ListItem {
  width: units.gu(5)
  height: units.gu(5)
  Button {
  activeFocusOnTab: false
  anchors {
  fill: parent
  margins: units.gu(1)
  }
  text: "Button #" + index
  }
  }
  }
  }

  Use TAB to select the first ListItem in the list. Pressing the LEFT
  arrow after that will put the focus on the Button in the first
  ListItem (you can see the focus outline changing).

  The same happens when using keyboard navigation to go to the last
  ListItem and then pressing the RIGHT cursor key.

  I could not reproduce the issue with a vertical ListView.

  This gives problems for the new Toolbar with scrolling icons inside
  it, because there I am wrapping an AbstractButton inside a ListItem in
  order to be able to get cursor key navigation until this bug is fixed:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1573616

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1590005/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1590005] Re: Focus can go be moved inside ListItem in a horizontal ListView

[Zsombor Egri]

Yes, now I can see it.

-- 
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/1590005

Title:
  Focus can go be moved inside ListItem in a horizontal ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Run this code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  model: 10
  orientation: ListView.Horizontal
  delegate: ListItem {
  width: units.gu(5)
  height: units.gu(5)
  Button {
  activeFocusOnTab: false
  anchors {
  fill: parent
  margins: units.gu(1)
  }
  text: "Button #" + index
  }
  }
  }
  }

  Use TAB to select the first ListItem in the list. Pressing the LEFT
  arrow after that will put the focus on the Button in the first
  ListItem (you can see the focus outline changing).

  The same happens when using keyboard navigation to go to the last
  ListItem and then pressing the RIGHT cursor key.

  I could not reproduce the issue with a vertical ListView.

  This gives problems for the new Toolbar with scrolling icons inside
  it, because there I am wrapping an AbstractButton inside a ListItem in
  order to be able to get cursor key navigation until this bug is fixed:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1573616

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1590005/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622742] Re: ActivityIndicator broken, likely due to Qt 5.6 update

[Zsombor Egri]

** Tags added: qt5.6

-- 
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/1622742

Title:
  ActivityIndicator broken, likely due to Qt 5.6 update

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  QML ActivityIndicator: file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

  The indicator isn't displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 
1.3.2073+16.04.20160824build1~~xenialoverlay1~1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 12 22:31:21 2016
  InstallationDate: Installed on 2016-05-06 (128 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1622742/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

-- 
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/1586013

Title:
  UITK Date picker broken on xenial

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6
  (right).

  More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting

  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml
  [...]
  FAIL!  : components::DatePicker13API::test_1_changeMinimumBeforeDate() 
Uncaught exception: Cannot call method hasOwnProperty of null
   Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1570478] Re: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1570478

Title:
  Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Update: Qt 5.6.1 and UITK 20160716:

  13 failures which MUST be fixed:
    dpr2
    dpr3
    performance

  --- original report ---
  Considerably less than on amd64 (bug #1560004), but still some now seen with 
the new UITK 20160412 and the latest Qt builds:

  1 failures which MUST be fixed:
    tst_performance

  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/performance/performance
  [...]
  #7  0x77c32034 in UCTheme::PaletteConfig::restorePalette() 
(this=0xeb8160) at ./src/Ubuntu/UbuntuToolkit/uctheme.cpp:278
  #8  0x77c2ebf3 in UCTheme::~UCTheme() (this=0xeb8160, 
__in_chrg=) at ./src/Ubuntu/UbuntuToolkit/uctheme_p.h:125

  https://launchpadlibrarian.net/253810125/buildlog_ubuntu-xenial-armhf
  .ubuntu-ui-
  toolkit_1.3.1938+16.04.20160412build1~xenial1~qt560~1_BUILDING.txt.gz

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1570478/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1590005] Re: activeFocusOnTab is ignored when Button is embedded inside ListItem in a horizontal ListView

[Zsombor Egri]

Input from UX: if a ListItem is used in a horizontal oriented ListView,
the horizontal navigation keys should focus the ListItems themselves,
and eventual active content focusing should be omitted no matter what is
the activeFocusOnTab setting is.

The https://code.launchpad.net/~zsombi/ubuntu-ui-
toolkit/dontFocusDisabledLi branch seem to fix this issue as well.

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/dontFocusDisabledLi

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1590005

Title:
  activeFocusOnTab is ignored when Button is embedded inside ListItem in
  a horizontal ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Run this code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  model: 10
  orientation: ListView.Horizontal
  delegate: ListItem {
  width: units.gu(5)
  height: units.gu(5)
  Button {
  activeFocusOnTab: false
  anchors {
  fill: parent
  margins: units.gu(1)
  }
  text: "Button #" + index
  }
  }
  }
  }

  Use TAB to select the first ListItem in the list. Pressing the LEFT
  arrow after that will put the focus on the Button in the first
  ListItem (you can see the focus outline changing).

  The same happens when using keyboard navigation to go to the last
  ListItem and then pressing the RIGHT cursor key.

  I could not reproduce the issue with a vertical ListView.

  This gives problems for the new Toolbar with scrolling icons inside
  it, because there I am wrapping an AbstractButton inside a ListItem in
  order to be able to get cursor key navigation until this bug is fixed:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1573616

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1590005/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1621509] Re: ListView with extension from UbuntuToolkit updates its model after the component is completed

[Zsombor Egri]

ListView extension is not active if someone explicitly uses ViewItems
attached properties or ListItem as delegate. As your sample doesn't use
either of these, it cannot be the culprit. You don't seem to use
anything from UITK so the only elements are instantiated at this time
are the context properties. However neither of those should have any
effect on the model setup.

-- 
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/1621509

Title:
  ListView with extension from UbuntuToolkit updates its model after the
  component is completed

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  This is the cause for the Sections index resetting after
  initialization, see bug 1610231.

  Create the file ModelTest.qml:

  import QtQuick 2.4

  Item {
  id: root
  width: 800
  height: 600

  ListView {
  model: root.model
  onModelChanged: print("LV model changed to "+model[0]+" "+model[1]+" 
"+model[2]+" "+model[3])
  Component.onCompleted: print("ListView completed.")
  }
  Component.onCompleted: print("root item completed.")

  property list objectList
  onObjectListChanged: print("root.objectList changed to "+objectList[0]+" 
"+objectList[1]+" "+objectList[2])
  property var model: objectList
  }

  And run this program modelInst.qml:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  ModelTest {
  QtObject {
  objectName: "one"
  id: objectOne
  }
  QtObject {
  objectName: "two"
  id: objectTwo
  }
  QtObject{
  objectName: "three"
  id: objectThree
  }

     objectList: [objectOne, objectTwo, objectThree]
  }

  The output is as follows:

  $ qmlscene modelInst.qml
  qml: root.objectList changed to undefined undefined undefined
  qml: root.objectList changed to QObject(0x118abf0, "one") undefined undefined
  qml: root.objectList changed to QObject(0x118abf0, "one") QObject(0x118a110, 
"two") undefined
  qml: root.objectList changed to QObject(0x118abf0, "one") QObject(0x118a110, 
"two") QObject(0x1182f80, "three")
  qml: LV model changed to QObject(0x118abf0, "one") QObject(0x118a110, "two") 
QObject(0x1182f80, "three") undefined
  qml: LV model changed to QObject(0x118abf0, "one") QObject(0x118a110, "two") 
QObject(0x1182f80, "three") undefined
  qml: root item completed.
  qml: ListView completed.
  qml: LV model changed to QObject(0x118abf0, "one") QObject(0x118a110, "two") 
QObject(0x1182f80, "three") undefined
  qml: LV model changed to QObject(0x118abf0, "one") QObject(0x118a110, "two") 
QObject(0x1182f80, "three") undefined

  So the model is changed AFTER the ListView and root item are
  completed.

  When the Ubuntu.Components import is removed the output is correct:

  $ qmlscene modelInst.qml
  qml: root.objectList changed to undefined undefined undefined
  qml: root.objectList changed to QObject(0x171c8d0, "one") undefined undefined
  qml: root.objectList changed to QObject(0x171c8d0, "one") QObject(0x171d290, 
"two") undefined
  qml: root.objectList changed to QObject(0x171c8d0, "one") QObject(0x171d290, 
"two") QObject(0x171d420, "three")
  qml: LV model changed to QObject(0x171c8d0, "one") QObject(0x171d290, "two") 
QObject(0x171d420, "three") undefined
  qml: LV model changed to QObject(0x171c8d0, "one") QObject(0x171d290, "two") 
QObject(0x171d420, "three") undefined
  qml: root item completed.
  qml: ListView completed.

  Also, if there is no ListView inside ModelTest.qml, then nothing is
  updated after the items are completed. So I suspect the issue is in
  our ListView extension.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1621509/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1573616] Re: ListView keyboard navigation focus using arrow keys only works with ListItem as a delegate

[Zsombor Egri]

A ListView can navigate with the horizontal or vertical keys (depending
on the orientation) *only* if is focused. This can be achieved by
setting the activeFocusOnTab: true or by setting the currentIndex
through a mouse button click. The ListViewProxy mentioned above it is
only active if the ListView has ViewItems attached properties defined
explicitly of the ListView uses ListItem as delegate (in which case the
ViewItems will automatically be attached). UbuntuListView doesn't use
ViewItems attached properties at all.

The bug is invalid :)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1573616

Title:
  ListView keyboard navigation focus using arrow keys only works with
  ListItem as a delegate

Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  We have this code to set the navigation focus for ListItems:

  void ListViewProxy::setKeyNavigationForListView(bool value)
  {
  UCListItem *listItem = qobject_cast(currentItem());
  if (listItem) {
  UCListItemPrivate::get(listItem)->setListViewKeyNavigation(value);
  listItem->update();
  }
  }

  We can at least add code to StyledItem (and update ListViewProxy) to
  make it work for that as well. I don't know if there can be a generic
  solution for Items as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1573616/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1620991] Re: Anchoring warnings in Buttons page in UITK Gallery

[Zsombor Egri]

The Flickable and the Scrollbar could be replaced with a ScrollView. The
Flickable stays inactive if the ComboButton content is set to be an
other Flickable. Having a ScrollView we could reparent it to the
visual's dropdown holder.

And we need to do this reparenting. The style's dropdown holder
specifies the area and the place of the dropdown, and the way it expands
(i.e. size expansion or overlay).

-- 
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/1620991

Title:
  Anchoring warnings in Buttons page in UITK Gallery

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-ui-toolkit/staging, r2090

  1) Build uitk
  2) run gallery with ./gallery.sh
  3) Open Buttons page

  Expected outcome: 
  no warnings

  Actual outcome:
  A few "QML Scrollbar: Cannot anchor to an item that isn't a parent or 
sibling."

  Explanation:
  That happens because Scrollbar anchors to the flickable item, but the 
ComboButton code has a hack that changes the parent of the Flickable to 
actually be Flickable's child. As a consequence  Flickable is not a sibling of 
the scrollbar anymore, thus producing the anchor-related warning.

  See http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  toolkit/staging/annotate/2090/src/Ubuntu/Components/1.3/ComboButton.qml#L354

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1620991/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1620991] Re: Anchoring warnings in Buttons page in UITK Gallery

[Zsombor Egri]

This worked without any warnings before.

-- 
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/1620991

Title:
  Anchoring warnings in Buttons page in UITK Gallery

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-ui-toolkit/staging, r2090

  1) Build uitk
  2) run gallery with ./gallery.sh
  3) Open Buttons page

  Expected outcome: 
  no warnings

  Actual outcome:
  A few "QML Scrollbar: Cannot anchor to an item that isn't a parent or 
sibling."

  Explanation:
  That happens because Scrollbar anchors to the flickable item, but the 
ComboButton code has a hack that changes the parent of the Flickable to 
actually be Flickable's child. As a consequence  Flickable is not a sibling of 
the scrollbar anymore, thus producing the anchor-related warning.

  See http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  toolkit/staging/annotate/2090/src/Ubuntu/Components/1.3/ComboButton.qml#L354

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1620991/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1620991] Re: Anchoring warnings in Buttons page in UITK Gallery

[Zsombor Egri]

I can confirm that revision 2045 brought these warnings in.

http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
toolkit/staging/revision/2045

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zsombor Egri (zsombi) => Andrea Bernabei (faenil)

-- 
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/1620991

Title:
  Anchoring warnings in Buttons page in UITK Gallery

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-ui-toolkit/staging, r2090

  1) Build uitk
  2) run gallery with ./gallery.sh
  3) Open Buttons page

  Expected outcome: 
  no warnings

  Actual outcome:
  A few "QML Scrollbar: Cannot anchor to an item that isn't a parent or 
sibling."

  Explanation:
  That happens because Scrollbar anchors to the flickable item, but the 
ComboButton code has a hack that changes the parent of the Flickable to 
actually be Flickable's child. As a consequence  Flickable is not a sibling of 
the scrollbar anymore, thus producing the anchor-related warning.

  See http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  toolkit/staging/annotate/2090/src/Ubuntu/Components/1.3/ComboButton.qml#L354

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1620991/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1611327] Re: Disabled ListItem inside ListView takes focus but does not show focus ring

[Zsombor Egri]

@Tim, @Femma: I guess you meant to scroll to the next enabled/disabled
item one by one, right?

-- 
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/1611327

Title:
  Disabled ListItem inside ListView takes focus but does not show focus
  ring

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Items outside of a ListView are skipped when using keyboard navigation
  to change the focus. However, a ListItem inside a ListView takes the
  focus even when it is disabled, but it does not show the focus frame
  when focused.

  For example, execute this QML program:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  delegate: ListItem {
  enabled: index != 2
  Label {
  anchors.centerIn: parent
  text: parent.enabled ? "enabled" : "disabled"
  }
  }
  model: 5
  }
  }

  Press TAB to focus on the ListView. Then press the down-cursor-key
  twice to move the focus down inside the ListView. The focus will be on
  the disabled item, but not focus frame is visible This is confusing
  for the user since the focus seems to disappear, and the Item where
  the focus seems to be (although invisible) cannot be triggered because
  it is disabled.

  Note: When fixing this bug, also test the solution for Horizontal
  ListViews (and RightToLeft and BottomToTop directions), since I
  encountered this bug in the scrolling toolbar (in progress) that has a
  Horizontal, RightToLeft ListView.

  ==UX Fix===

  Bypass focus for a disabled item and show focus immediately for the
  next available enabled item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1611327/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1611327] Re: Disabled ListItem inside ListView takes focus but does not show focus ring

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1611327

Title:
  Disabled ListItem inside ListView takes focus but does not show focus
  ring

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Items outside of a ListView are skipped when using keyboard navigation
  to change the focus. However, a ListItem inside a ListView takes the
  focus even when it is disabled, but it does not show the focus frame
  when focused.

  For example, execute this QML program:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  delegate: ListItem {
  enabled: index != 2
  Label {
  anchors.centerIn: parent
  text: parent.enabled ? "enabled" : "disabled"
  }
  }
  model: 5
  }
  }

  Press TAB to focus on the ListView. Then press the down-cursor-key
  twice to move the focus down inside the ListView. The focus will be on
  the disabled item, but not focus frame is visible This is confusing
  for the user since the focus seems to disappear, and the Item where
  the focus seems to be (although invisible) cannot be triggered because
  it is disabled.

  Note: When fixing this bug, also test the solution for Horizontal
  ListViews (and RightToLeft and BottomToTop directions), since I
  encountered this bug in the scrolling toolbar (in progress) that has a
  Horizontal, RightToLeft ListView.

  ==UX Fix===

  Bypass focus for a disabled item and show focus immediately for the
  next available enabled item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1611327/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567924] Re: App crashes when using StyledItem + Ubuntu.Layouts

[Zsombor Egri]

Does it happen with any other setup than ScrollView?

-- 
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/1567924

Title:
  App crashes when using StyledItem + Ubuntu.Layouts

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  This is something that I've seen often while testing Ubuntu Document
  Viewer on desktop.

  *** Using Document Viewer:

  1) Launch DocViewer
  2) Open a LibreOffice presentation document
  3) A sidebar with the list of slides is placed at the left of the window
  4) Resize the window so that its width is less than units.gu(120)
  5) The list of slides is now visible at the bottom of the window
  6) If the app hasn't crashed yet, resize the window so that: width > 
units.gu(120)
  7) Repeat 3, 4, 5, 6.

  - What happens?
  DocViewer crash.

  
  *** Using the minimal example below:

  1) Launch the .qml file
  2) A blue rectangle is visible on the screen
  3) On a phone: rotate the screen to landscape (from portrait)
   On a desktop: resize the window so that height > width
  4) On a phone: rotate back to portrait
   On a desktop: resize the window so that width > height

   - What should happen?
  The rectangle becomes yellow.

  - What happens?
  On the phone: the rectangle is still blue. A black surface becomes visible on 
the bottom. The app has crashed.
  On the desktop: the app crashes.

  ==

  Tested on a BQ E5, with rc-proposed (r302)
  Tested on desktop, vivid+overlay, UITK version: 
1.3.1872+201602271301-staging-0+1.3.1795+16.04.20160106~ubuntu15.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1567924/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567924] Re: App crashes when using StyledItem + Ubuntu.Layouts

[Zsombor Egri]

I see the crash happening when the conditional layouts are trying to set
a property which for some reason bothers the theming implementation. The
ascendant themed item lookup may be in trouble there, so it seems a
theming FW bug.

-- 
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/1567924

Title:
  App crashes when using StyledItem + Ubuntu.Layouts

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  This is something that I've seen often while testing Ubuntu Document
  Viewer on desktop.

  *** Using Document Viewer:

  1) Launch DocViewer
  2) Open a LibreOffice presentation document
  3) A sidebar with the list of slides is placed at the left of the window
  4) Resize the window so that its width is less than units.gu(120)
  5) The list of slides is now visible at the bottom of the window
  6) If the app hasn't crashed yet, resize the window so that: width > 
units.gu(120)
  7) Repeat 3, 4, 5, 6.

  - What happens?
  DocViewer crash.

  
  *** Using the minimal example below:

  1) Launch the .qml file
  2) A blue rectangle is visible on the screen
  3) On a phone: rotate the screen to landscape (from portrait)
   On a desktop: resize the window so that height > width
  4) On a phone: rotate back to portrait
   On a desktop: resize the window so that width > height

   - What should happen?
  The rectangle becomes yellow.

  - What happens?
  On the phone: the rectangle is still blue. A black surface becomes visible on 
the bottom. The app has crashed.
  On the desktop: the app crashes.

  ==

  Tested on a BQ E5, with rc-proposed (r302)
  Tested on desktop, vivid+overlay, UITK version: 
1.3.1872+201602271301-staging-0+1.3.1795+16.04.20160106~ubuntu15.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1567924/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1611327] Re: Disabled ListItem inside ListView takes focus but does not show focus ring

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

-- 
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/1611327

Title:
  Disabled ListItem inside ListView takes focus but does not show focus
  ring

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Items outside of a ListView are skipped when using keyboard navigation
  to change the focus. However, a ListItem inside a ListView takes the
  focus even when it is disabled, but it does not show the focus frame
  when focused.

  For example, execute this QML program:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  delegate: ListItem {
  enabled: index != 2
  Label {
  anchors.centerIn: parent
  text: parent.enabled ? "enabled" : "disabled"
  }
  }
  model: 5
  }
  }

  Press TAB to focus on the ListView. Then press the down-cursor-key
  twice to move the focus down inside the ListView. The focus will be on
  the disabled item, but not focus frame is visible This is confusing
  for the user since the focus seems to disappear, and the Item where
  the focus seems to be (although invisible) cannot be triggered because
  it is disabled.

  Note: When fixing this bug, also test the solution for Horizontal
  ListViews (and RightToLeft and BottomToTop directions), since I
  encountered this bug in the scrolling toolbar (in progress) that has a
  Horizontal, RightToLeft ListView.

  ==UX Fix===

  Bypass focus for a disabled item and show focus immediately for the
  next available enabled item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1611327/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

[Zsombor Egri]

@zhang woh!!! It works!!! Thanks for that! We can finally
proceed on UITK and System Settings app side then.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1433590

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  

[Touch-packages] [Bug 1611327] Re: Disabled ListItem inside ListView takes focus but does not show focus ring

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

-- 
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/1611327

Title:
  Disabled ListItem inside ListView takes focus but does not show focus
  ring

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Items outside of a ListView are skipped when using keyboard navigation
  to change the focus. However, a ListItem inside a ListView takes the
  focus even when it is disabled, but it does not show the focus frame
  when focused.

  For example, execute this QML program:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  delegate: ListItem {
  enabled: index != 2
  Label {
  anchors.centerIn: parent
  text: parent.enabled ? "enabled" : "disabled"
  }
  }
  model: 5
  }
  }

  Press TAB to focus on the ListView. Then press the down-cursor-key
  twice to move the focus down inside the ListView. The focus will be on
  the disabled item, but not focus frame is visible This is confusing
  for the user since the focus seems to disappear, and the Item where
  the focus seems to be (although invisible) cannot be triggered because
  it is disabled.

  Note: When fixing this bug, also test the solution for Horizontal
  ListViews (and RightToLeft and BottomToTop directions), since I
  encountered this bug in the scrolling toolbar (in progress) that has a
  Horizontal, RightToLeft ListView.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1611327/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552928] Re: New bottom edge component is harder to flick up

[Zsombor Egri]

The BottomEdge design guides state that if a gesture ends less than
1/3rd of the screen, it should collapse back. There was no mentioning on
quick flicks, and we discussed this with them back then, and we agreed
that we will implemented the swipe gesture for now. I think we need to
revisit this with design.

-- 
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/1552928

Title:
  New bottom edge component is harder to flick up

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I usually hold the phone in one hand and open the bottom edge by
  flicking up from the bottom with the thumb. This worked fine with the
  previous bottom edge, however, with the new one, there seems to be
  larger amount of dragging required. I keep on failing to open the
  bottom edge in the messages-app and clock app, now that they use the
  new component.

  When dragging very slowly such an big required distance does make
  sense, but for quick flicks with the thumb, it should also take the
  speed and/or touch points history into account and reduce the required
  distance if it detects a fast flick gesture.

  In the right edge implementation for instance, it tracks the touch
  points and already activates the gesture after a rather short distance
  (2 grid units), provided it is a one-way gesture with increasing
  distance from the edge in each recognized point. Such a logic would
  imo also make sense for the bottom edge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552928/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1604780] [NEW] null initializer properties handed over to AdaptivePageLayout or PageStack page adding functions cause error

[Zsombor Egri]

Public bug reported:

If a page is added to AdaptivePageLayout or PageStack with an
initializer list, where an initial value is set to null, the null value
causes "Cannot convert to QVariant::<type*> from QVariant::void*" error
to be shown. The error is provided by the PageWrapper 1.3
implementation.

This works with 1.2 PageStack and PageWrapper (all QML).

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Zsombor Egri (zsombi)
 Status: In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

-- 
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/1604780

Title:
  null initializer properties handed over to AdaptivePageLayout or
  PageStack page adding functions cause error

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  If a page is added to AdaptivePageLayout or PageStack with an
  initializer list, where an initial value is set to null, the null
  value causes "Cannot convert to QVariant::<type*> from
  QVariant::void*" error to be shown. The error is provided by the
  PageWrapper 1.3 implementation.

  This works with 1.2 PageStack and PageWrapper (all QML).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1604780/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1603452] Re: [SDK] Change leading action background to red and icon to white

[Zsombor Egri]

> What Design wants, from what I understood, is an easy way for developers to 
> specify that an action is destructive/neutral/positive, something like that.
That way, the developer specifies the kind of action, and the SDK takes care of 
using the right colour, following the guidelines provided by the Design team.

It could be a new property in Action, or it could be a delegate
template, such as ActionDelegate { property Enum type:
destructive/neutral/positive ... etc etc ... }

Right... and this would bring new values in Palette each... I'd try to
avoid that. Also I'd try to avoid classifying the actions into these
criteria. Or any criteria. It is all about the visualization of a
specific action, the Action should not have any hints for the visuals...
Also, what if a developer decides to color the same way his icons as the
default negative action is colored?

We had yesterday a HO with Rae and Jamie, let's hope they will update
the bug with the solution soon.

-- 
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/1603452

Title:
  [SDK] Change leading action background to red and icon to white

Status in Ubuntu UI Toolkit:
  New
Status in Ubuntu UX:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  We'd like to change the leading action background from light grey back
  to red. And switch the icon from red to white. However, I have spoken
  to Andrea and the problem is regarding when a leading action is
  disabled. Outlined as follows:

  the default action delegate is just an Item { Icon {} } so it has no
  background, see: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-
  ui-
  
toolkit/staging/view/2033/src/Ubuntu/Components/Themes/Ambiance/1.3/ListItemStyle.qml#L120

  Moreover, the whole ListItemActions panel uses only one colour for the
  background http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  
toolkit/staging/view/2033/src/Ubuntu/Components/Themes/Ambiance/1.3/ListItemStyle.qml#L51

  Therefore if there are several actions in the leading action slot, all
  will be disabled. Can we change the API so that there is flexibility
  when choosing one action to be disabled rather than all of them?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1603452/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1604509] Re: In the bottom edge component, using preload=true with contentUrl results in an empty page

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

-- 
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/1604509

Title:
  In the bottom edge component, using preload=true with contentUrl
  results in an empty page

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In the bottom edge component, using preload=true with contentUrl
  results in an empty page.

  For example the following code 'works' with a red rectangle in the
  bottom edge:

  BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
  }

  But the following code does not and results in a transparent overlay,
  the contentItem appears to stay null.

  BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
preloadContent: true
  }

  Note that using contentComponent does work with preloadContent true or false.
  See the linked branch for an example of this not working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1604509/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1603452] Re: [SDK] Change leading action background to red and icon to white

[Zsombor Egri]

"Therefore if there are several actions in the leading action slot, all
will be disabled. Can we change the API so that there is flexibility
when choosing one action to be disabled rather than all of them?"

That is not true. Beware that the disabled state is not for the
background mainly, but for the text color. And the icon color is enabled
sensible, meaning it uses different colors for enabled or disabled
state.

As we discussed once with Rae, there are some possibilities for
coloring:

[16:20:12]  hi zsombor quick question, what colour are we 
currently using for the background of leading and trailing actions?
[17:27:56]  oh, sorry, I did not seen your ping'
[17:28:48]  it is normal.foreground
[17:32:04]  can we have different variations of it? basically 
what we want to do now is have a set to choose from depending on how severe the 
action is. e.g. red for delete, foreground for dismiss or hide
[17:32:52]  well, the icon color is red now for delete, the background 
is different
[17:33:50]  if you want to do that per action, the list panels will 
look like clothes from '60s
[17:35:46]  well we were wanting to change it back to red 
background and white icon but only for actions like delete. we have some other 
instances, like “dismiss” in notifications and “remove” in group chat where we 
want to use foreground (light and dark) and  .foreground text
[17:36:31]  when these instances are in red, they look way too 
severe. like in group chat, removing someone from a chat group looks like you 
are removing them from your address book
[17:36:36]  but if you combine those with other actions, they will have 
different backgrounds... it may be what you want though...
[17:36:56]  you mean if we had two leading actions for instance?
[17:37:15]  yes
[17:37:39]  I know we advice not to, but if apps put sthing else, 
they'll have it in pepita
[17:38:49]  well our recommendation is to use leading actions for 
destructive and trailing for positive/neutral . if they break this, then yes, 
could look a but weird. but that’s why it would be great to have options to 
choose from. if not red, then a more neutral look like .foreground and 
.foregorund text
[17:39:22]  is there a way to have a variation like this?
[17:39:28]  ok... well, we can change the panel color into red, np, 
like I can use negative there
[17:40:05]  otoh, we don't have the ability to colorize the action 
colors individually, for that a custom delegate (painter) must be declared
[17:40:23]  right, we would want it back to red for things like 
delete. but not for every leading action….what do you mean?
[17:40:44]  well, that is something we cannot drive automatically
[17:40:53]  that's what I meant
[17:41:09]  we don't know whether an action is negative or not
[17:42:16]  so if someone wanted it changed, they’d have to do it 
themselves, can it be overridden in the SDK? or do they have to build the whole 
component from scratch?
[17:42:25]  yes
[17:42:35]  they have to color it themselves
[17:42:41]  that's th edelegate
[17:42:55]  but can still use the SDK component though
[17:42:56]  the delegate paints/views the action
[17:42:59]  yes
[17:43:17]  so it’s just a matter of us deciding to make the 
default neutral or red
[17:43:23]  yep
[17:43:46]  i’ll will talk to the others about it
[17:43:52]  thanks for the info 
[17:43:55]  yw

-- 
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/1603452

Title:
  [SDK] Change leading action background to red and icon to white

Status in Ubuntu UI Toolkit:
  New
Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  We'd like to change the leading action background from light grey back
  to red. And switch the icon from red to white. However, I have spoken
  to Andrea and the problem is regarding when a leading action is
  disabled. Outlined as follows:

  the default action delegate is just an Item { Icon {} } so it has no
  background, see: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-
  ui-
  
toolkit/staging/view/2033/src/Ubuntu/Components/Themes/Ambiance/1.3/ListItemStyle.qml#L120

  Moreover, the whole ListItemActions panel uses only one colour for the
  background http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  
toolkit/staging/view/2033/src/Ubuntu/Components/Themes/Ambiance/1.3/ListItemStyle.qml#L51

  Therefore if there are several actions in the leading action slot, all
  will be disabled. Can we change the API so that there is flexibility
  when choosing one action to be disabled rather than all of them?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1603452/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 1603353] Re: Move BottomEdge between columns in AdaptivePageLayout

[Zsombor Egri]

** Tags added: apl

-- 
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/1603353

Title:
  Move BottomEdge between columns in AdaptivePageLayout

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  In several apps (address-book and messaging-app), the Page to which
  the BottomEdge is attached depends on the number of columns in
  AdaptivePageLayout (APL).

  In the description below, we assume that mainPage is the primary page
  in the APL and is always displayed in the first column. Depending on
  the screen/window size the APL can have 1 or 2 columns, and a
  detailPage can be opened from mainPage and is added to the second
  column.

  In 1-column mode, the bottom edge is attached to the current page in
  the first column (mainPage or detailPage).

  In 2-column mode, the bottom edge is attached to detailPage, and when
  it is open it is displayed in the second column. The bottom edge in
  the second column can be opened from a header action in the first
  column (see specs [1]).

  It must be possible to switch between 1 and 2 columns at any time, and
  if the bottom edge was opened in 1-column mode and displayed in the
  first column, it should automatically move to the second column when
  switching to 2-column mode, and vice versa.

  This functionality may already be possible in APL by attaching
  identical BottomEdges to the two pages, and when BottomEdge is opened,
  to add a BottomEdgePage to the APL so that the APL then automatically
  moves that page when switching between layouts. But we need to
  demonstrate how to do this with an example in the documentation.

  [1] specifications for convergence in telephony apps:
  
https://docs.google.com/presentation/d/1ZY9WSsEhDnE8MW6ou8GeGNM8isPVgNvl7i5PzbICmUo/edit?ts=56a2605c#slide=id.gfdd4eed78_0_41

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1603353/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1534674] Re: [AdaptivePageLayout] Add function to return the top Page of a PageColumn

[Zsombor Egri]

** Tags removed: adaptivepagelayout
** Tags added: apl

-- 
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/1534674

Title:
  [AdaptivePageLayout] Add function to return the top Page of a
  PageColumn

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  Add a function that will return a reference to the top Page object in
  a specific PageColumn.

  Suggestion:

  getPageInColumn(int columnIndex)

  Use Case:

  In uReadIt I have at most a 3-column layout. I would like a user
  action on an item in the first column to add a Page to the 3rd column.
  This requires knowing the current page in the 2nd column in order to
  call pageStack.addPageToNextColumn(secondPage, "SourcePage.qml").

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1534674/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1534674] Re: [AdaptivePageLayout] Add function to return the top Page of a PageColumn

[Zsombor Egri]

** Tags added: convergence

-- 
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/1534674

Title:
  [AdaptivePageLayout] Add function to return the top Page of a
  PageColumn

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  Add a function that will return a reference to the top Page object in
  a specific PageColumn.

  Suggestion:

  getPageInColumn(int columnIndex)

  Use Case:

  In uReadIt I have at most a 3-column layout. I would like a user
  action on an item in the first column to add a Page to the 3rd column.
  This requires knowing the current page in the 2nd column in order to
  call pageStack.addPageToNextColumn(secondPage, "SourcePage.qml").

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1534674/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1551349] Re: Make ListItem automatically bind to the height of a SlotsLayout/ListItemLayout when that's the only content

[Zsombor Egri]

No work was yet scheduled for this.

-- 
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/1551349

Title:
  Make ListItem automatically bind to the height of a
  SlotsLayout/ListItemLayout when that's the only content

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-ui-toolkit r1873

  Currently, when creating a list item, the developer has to manually
  bind the height of the ListItem to that of ListItemLayout that it
  contains.

  Since this is not intuitive in QML (you usually bind content's size to
  parent's, not the opposite), we're seeing that the developers most of
  the times forget to add that binding.

  Proof: even the UI Components Gallery was not doing it, and as a result the 
labels in the list items of the left panel were *slightly* offset.
  
https://code.launchpad.net/~faenil/ubuntu-ui-toolkit/fixListItemAlignmentUIGallery/+merge/287492

  If the developer doesn't add that binding, the ListItem usually ends
  up being shorter in height than the ListItemLayout (or SlotsLayout) it
  contains.

  This is usually not a big issue because the deafult ListItem height is
  enough to show a couple of labels in a column, so the developer will
  usually not realize that he's done something wrong, but the vertical
  alignment of the slots will be wrong, because it's computed relative
  to ListItemLayout's height, not ListItem's (since ListItemLayout
  resizes dynamically by design to accomodate all the slots).

  In the worst case (very tall ListItemLayout/SlotsLayout with lots of
  text), ListItem layout will clip part of the content.

  My proposal is that we handle this automatically.
  The developer should not have to care about this detail, because 
ListItem+ListItemLayout/SlotsLayout is the our main and most important usecase 
for those components, so it should work straight out of the box and be as 
simple as possible to implement.

  My solution (although I only know ListItemLayout/SlotsLayout's code, not 
ListItem's):
  - change ListItem so that when a new child is added (content), it checks if 
that child is a SlotsLayout-derived component. If that is the case, and if 
that's the only child, then ListItem binds to content's height.

  NOTE: the solution described above is just a proposal, please make sure that 
the implementation doesn't prevent the dev from overriding or changing the 
behaviour if needed. 
  Moreover, I think the binding should not be created automatically if there's 
more than one child (which I think is then case when using ListItem's 
"expansion" mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1551349/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

[Zsombor Egri]

On Wed, Jul 13, 2016 at 10:41 AM, Zhang Enwei 
wrote:

> I am now investigating if org.freedesktop.DBus.GetConnectionUnixProcessID
> is supported in go-dbus.
> If it is supported, we can use pid to get the name of the process or path
> of the binary.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1433590
>
> Title:
>   apparmor dbus denial for org.freedesktop.Accounts and make Other
>   vibrations work
>
> Status in Canonical System Image:
>   Triaged
> Status in apparmor-easyprof-ubuntu package in Ubuntu:
>   Fix Released
> Status in ubuntu-system-settings package in Ubuntu:
>   Confirmed
> Status in ubuntu-ui-toolkit package in Ubuntu:
>   Confirmed
> Status in usensord package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This affects vivid and (somewhat recently?) 14.09.
>
>   At some point, apps started to request access to
>   org.freedesktop.Accounts for something, but I'm not sure what. It has
>   been conjectured in this bug that it is due to vibration settings.
>   Filing against ubuntu-system-settings for now, but please feel free to
>   move to the correct package.
>
>   This happens with webapps:
>   Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED"
> operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts"
> interface="org.freedesktop.DBus.Introspectable" member="Introspect"
> mask="send" name="org.freedesktop.Accounts" pid=2632
> profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26"
> peer_pid=1596 peer_profile="unconfined"
>   Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED"
> operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts"
> interface="org.freedesktop.Accounts" member="FindUserById" mask="send"
> name="org.freedesktop.Accounts" pid=2632
> profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26"
> peer_pid=1596 peer_profile="unconfined"
>
>   and QML apps:
>   Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED"
> operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts"
> interface="org.freedesktop.DBus.Introspectable" member="Introspect"
> mask="send" name="org.freedesktop.Accounts" pid=3377
> profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596
> peer_profile="unconfined"
>   Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED"
> operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts"
> interface="org.freedesktop.Accounts" member="FindUserById" mask="send"
> name="org.freedesktop.Accounts" pid=3377
> profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596
> peer_profile="unconfined"
>
>   The following rules allow the requested access:
> dbus (send)
>  bus=system
>  path="/org/freedesktop/Accounts"
>  interface="org.freedesktop.DBus.{Introspectable,Properties}"
>  member=Introspect
>  peer=(name=org.freedesktop.Accounts,label=unconfined),
> dbus (send)
>  bus=system
>  path="/org/freedesktop/Accounts"
>  interface="org.freedesktop.Accounts"
>  member=FindUserById
>  peer=(name=org.freedesktop.Accounts,label=unconfined),
> dbus (send)
>  bus=system
>  path="/org/freedesktop/Accounts/User[0-9]*"
>  interface="org.freedesktop.DBus.Properties"
>  member=Get
>  peer=(name=org.freedesktop.Accounts,label=unconfined),
>
>   However, the above is too lenient and constitutes a privacy leak for
>   apps. FindUserById could be used by a malicious app to enumerate
>   usernames on multiuser systems and because we can't mediate method
>   data with apparmor, the Get() method can be used to obtain any
>   information provided by this interface.
>
>   The following can be used to see what can be leaked to a malicious app:
>   gdbus introspect --system -d org.freedesktop.Accounts -o
> /org/freedesktop/Accounts/User`id -u phablet`
>
>   This can be solved in a couple of ways:
>   1. add whatever information the app is trying to access to a new helper
> service that only exposes things that the app needs. This could be a single
> standalone service, perhaps something from ubuntu-system-settings, that
> could expose any number of things-- the current locale, if the locale
> changed, if the grid units changed, the vibration settings, etc. Since this
> service wouldn't have any sensitive information, you could use standard
> dbus properties/Get()/etc
>   2. add a new dbus API to an existing service such that apparmor rules
> can then be used to allow by method (eg, GetVibration() or something)
>
>   I won't dictate the implementation except to mention that '1' seems
>   like something generally useful and I believe that it was something
>   the ubuntu-system-settings devs were already looking at for detecting
>   locale changes without rebooting.
>
>
>   Original description
>   starting an app in vivid 

[Touch-packages] [Bug 1600177] Re: Keyboard Shortcut doesn't work when the action is in the overflow button

[Zsombor Egri]

Question: does the action, which is not in the overflow, get triggered
by the shortcut assigned to it? I suspect it does.

The thing is, once the action goes into the overflow, it will be
deactivated as long as the overflow is shown. This is due to
ActionSelectionPopover being used by the overflow, which has its own
ActionContext (PopupContext), which is inactive as long as it is not
getting visible.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zsombor Egri (zsombi) => Tim Peeters (tpeeters)

-- 
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/1600177

Title:
  Keyboard Shortcut doesn't work when the action is in the overflow
  button

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  EXPECTED RESULT:
  Performing the keyboard shortcut should trigger the action.

  ACTUAL RESULT:
  Performing the keyboard shortcut does nothing and no indication of an error 
in the log

  STEPS TO REPRODUCE:
  1. Add actions in the trailingActionBar of a page header.
  2. Add keyboard shortcut to these actions i.e. "Ctrl+F"
  3. Set the numberOfSlots property to 1 so that all actions are in the 
overflow button.
  4. Try to perform the keyboard shortcuts

  
  Framework Version: ubuntu-sdk-15.04.5
  Device: Nexus 7 (rc-proposed) and bq E5 HD (OTA 11)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1600177/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567380] Re: Bottom edge arrow looks lo-res

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1567380

Title:
  Bottom edge arrow looks lo-res

Status in Ubuntu UX:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The bottom edge arrow introduced in OTA-10 is pixelated and does not
  look very good. This is especially visible with a dark theme. The
  Timer app is a good way to see this since it uses the standard
  components and you can change the theme very easily.

  

  The asset has been replaced and released

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1567380/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1595461] [NEW] API file uses namespace inconsistently

[Zsombor Egri]

Public bug reported:

With the recent move of c++ types from Ubuntu.Components plugin into
UbuntuToolkit and embedding them into a namespace caused API dump to use
the namespace inconsistently. In some places has a "." in other places a
"::".

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Christian Dywan (kalikiana)
 Status: Confirmed

-- 
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/1595461

Title:
  API file uses namespace inconsistently

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  With the recent move of c++ types from Ubuntu.Components plugin into
  UbuntuToolkit and embedding them into a namespace caused API dump to
  use the namespace inconsistently. In some places has a "." in other
  places a "::".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1595461/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1594400] Re: Wrong statement about "persistentSelection" property of TextArea

[Zsombor Egri]

This has been a copy+paste from Qt doc. So if someone disagrees, can
comment to Qt :)

-- 
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/1594400

Title:
  Wrong statement about "persistentSelection" property of TextArea

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In the documentation for UITK TextArea[1]:
  "Whether the TextArea should keep the selection visible when it loses 
active focus to another item in the scene. By default this is set to true;"

  In the documentation for QML TextEdit component (inherited by UITK TextArea):
  "Whether the TextEdit should keep the selection visible when it loses 
active focus to another item in the scene. By default this is set to false."

  The component from UITK[3] only set an alias to the TextEdit property,
  without changing its default value. This leads to an unexpected
  behaviour whenever the default property is set to a different value by
  the upstream project.

  In Qt 5.0.2 the property was set to true[4]. Since Qt 5.1.1, the value
  has been changed[5].

  

  [1] 
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.TextArea/
  [2] http://doc.qt.io/qt-5/qml-qtquick-textedit.html#persistentSelection-prop

  [3] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  toolkit/staging/view/head:/src/Ubuntu/Components/1.3/TextArea.qml

  [4] 
http://qt.apidoc.info/5.0.2/qtquick/qml-qtquick2-textedit.html#persistentSelection-prop
  [5] 
http://qt.apidoc.info/5.1.1/qtquick/qml-qtquick2-textedit.html#persistentSelection-prop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1594400/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1591908] Re: Unit tests fail on Yakketi

[Zsombor Egri]

Indeed, Yakkety has Qt 5.6 (so far) which brings some conceptual changes
in the Qt internals which we are relying on. So far we managed to make
them build, but that is not enough, as some functionality differs from
how it used to be thus our tests fail.

As our target is not yet Yakkety but Vivid and Xenial, the bug can be
classified as high importance. Should the decision be made to switch to
Yakkety, we will rise its importance.

In addition, here is a list of Qt 5.6 related bugs we must target:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
toolkit/+bugs?field.tag=qt5.6

-- 
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/1591908

Title:
  Unit tests fail on Yakketi

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Many of the UITK unit tets fail on Yakketi because Yakketi has newer
  Qt than Xenail and Vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1591908/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1590005] Re: activeFocusOnTab is ignored when Button is embedded inside ListItem in a horizontal ListView

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

-- 
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/1590005

Title:
  activeFocusOnTab is ignored when Button is embedded inside ListItem in
  a horizontal ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Run this code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  model: 10
  orientation: ListView.Horizontal
  delegate: ListItem {
  width: units.gu(5)
  height: units.gu(5)
  Button {
  activeFocusOnTab: false
  anchors {
  fill: parent
  margins: units.gu(1)
  }
  text: "Button #" + index
  }
  }
  }
  }

  Use TAB to select the first ListItem in the list. Pressing the LEFT
  arrow after that will put the focus on the Button in the first
  ListItem (you can see the focus outline changing).

  The same happens when using keyboard navigation to go to the last
  ListItem and then pressing the RIGHT cursor key.

  I could not reproduce the issue with a vertical ListView.

  This gives problems for the new Toolbar with scrolling icons inside
  it, because there I am wrapping an AbstractButton inside a ListItem in
  order to be able to get cursor key navigation until this bug is fixed:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1573616

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1590005/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1576302] Re: Cannot use keyboard to navigate the UITK gallery in single-column mode

[Zsombor Egri]

Hold on ListView navigation is possibl eONLY if the ListView is
focused. If the focused item is a Header action, the up/down keys will
NOT be captured by the ListView. It is illogical that up/down keys
should be grabbed by the ListView even if it has no focus.

Enter/Return/Space key handling si in a separate MR. Should the Space
key also act as Enter on ListItems? Or only on Buttons?

-- 
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/1576302

Title:
  Cannot use keyboard to navigate the UITK gallery in single-column mode

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Start the UITK gallery, and resize the window to have a single column.

  Now, with TAB you can navigate between the actions in the header, and
  the ListView with that list the different Pages with components. But
  it is not possible to use the arrow keys to select a ListItem, and
  then press ENTER/SPACE to open that page, because pressing the arrow
  (up/down) key automatically triggers the ListItem (onClicked?) and
  opens the Page. So only the first Page (ActionBar) can be opened using
  keyboard navigation when you have only one column.

  UX Fix: 
  In a single column view only the arrow keys for selection should be turned 
off and just move up and down the list, to select enter should be used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1576302/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1531814] Re: Syntax highlighting broken for ListItem

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

** Changed in: canonical-developer-experience
   Status: Confirmed => Invalid

-- 
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/1531814

Title:
  Syntax highlighting broken for ListItem

Status in Client Developer Experience:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  ListItem is not recognized by the syntax highlighter (and with that no
  code completion for it)

  http://i.imgur.com/hEDwMYR.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1531814/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1531815] Re: Syntax highlighting broken for UbuntuShape

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

** Changed in: canonical-developer-experience
   Status: Confirmed => Invalid

-- 
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/1531815

Title:
  Syntax highlighting broken for UbuntuShape

Status in Client Developer Experience:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Syntax highlighting not working for UbuntuShape, and with that also no
  code completion for it:

  http://i.imgur.com/sh3aogD.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1531815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1531815] Re: Syntax highlighting broken for UbuntuShape

[Zsombor Egri]

Michael, it was never the UITK problem, but qmlplugindump one. Despite
we create the types file in UITK, QtCreator will run qmlplugindump
again, and that overrides the types we gave.

-- 
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/1531815

Title:
  Syntax highlighting broken for UbuntuShape

Status in Client Developer Experience:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Syntax highlighting not working for UbuntuShape, and with that also no
  code completion for it:

  http://i.imgur.com/sh3aogD.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1531815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1582339] Re: Selected section has no color

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1582339

Title:
  Selected section has no color

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  The last change of the pallet broke the selected section's coloring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1582339/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1575060] Re: APL divider goes on top of column content

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1575060

Title:
  APL divider goes on top of column content

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  The APL divider will hide part of the column content. To work around
  this and to avoid the right edge of the focus frame for uclistitem to
  be hidden by the APL divider, uclistitem has this code on line 1143:
  rect -= QMarginsF(0, 0, UCUnits::instance()->dp(1), 0);

  That causes a bug with the sections  focus frame (which is the
  ListItem focus frame), there is a 'gap' of 1 pixel wide on the right-
  hand side of the focus frame which looks wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575060/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1531814] Re: Syntax highlighting broken for ListItem

[Zsombor Egri]

It was the qmlplugindump which did not resolve few types properly. Sorry
for the inconvenience. Can we close the bug?

-- 
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/1531814

Title:
  Syntax highlighting broken for ListItem

Status in Client Developer Experience:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  ListItem is not recognized by the syntax highlighter (and with that no
  code completion for it)

  http://i.imgur.com/hEDwMYR.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1531814/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1584232] Re: trailingActions overlaps APL

[Zsombor Egri]

The clipping could be in the APL column holder. So that can be auto-set
in the APL itself.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Tags added: convergence

-- 
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/1584232

Title:
  trailingActions overlaps APL

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  When using trailingActions with APL(AdaptivePageLayout) on tablets

  Screenshots on Nexus 7 with rc-proposed r443

  
https://www.flickr.com/photos/44748317@N08/27137523815/in/album-72157667368951370/
  
https://www.flickr.com/photos/44748317@N08/26533213893/in/album-72157667368951370/
  
https://www.flickr.com/photos/44748317@N08/27042409572/in/album-72157667368951370/
  
https://www.flickr.com/photos/44748317@N08/26533213663/in/album-72157667368951370/

  Code example: 
  http://pastebin.ubuntu.com/16537177/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1584232/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1531814] Re: Syntax highlighting broken for ListItem

[Zsombor Egri]

I have a different one... Perhaps we should check it again.

http://imgur.com/3snAsHX

-- 
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/1531814

Title:
  Syntax highlighting broken for ListItem

Status in Client Developer Experience:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  ListItem is not recognized by the syntax highlighter (and with that no
  code completion for it)

  http://i.imgur.com/hEDwMYR.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1531814/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1582339] Re: Selected section has no color

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1582339

Title:
  Selected section has no color

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The last change of the pallet broke the selected section's coloring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1582339/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1582339] Re: Selected section has no color

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Tim Peeters (tpeeters) => Zsombor Egri (zsombi)

-- 
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/1582339

Title:
  Selected section has no color

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The last change of the pallet broke the selected section's coloring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1582339/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1580627] Re: ComboButton is not propagating the click event

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

-- 
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/1580627

Title:
  ComboButton is not propagating the click event

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  ListView delegate is not receiving the click event.

  Check attached example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580627/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1575430] Re: App very slow, great lag after update 2.2.4

[Zsombor Egri]

** Project changed: ubuntu-ui-toolkit => ubuntu-ui-toolkit (Ubuntu)

-- 
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/1575430

Title:
  App very slow, great lag after update 2.2.4

Status in Telegram app:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  well chaps, subject nails it.
  Ever since the upgrade to version 2.2.4 for Telegram on Ubuntu phone, there 
is an enormous lag on the app.
  When clicking to select a conversation or group, it marks it as grey and 
takes between 4 to 8 seconds to open it. And another 3 seconds, on average, to 
load a conversation. Text only, not loading any images.

  The reason I'm filling this one is that the difference from the
  previous version is quite noticeable. Prior to this update, it was
  very fluid. And enjoyable to use.

  I'm using a BQ Aquaris E4.5 Ubuntu Edition on Ota 10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/telegram-app/+bug/1575430/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1545118] Re: [AdaptivePageLayout] can't easily grab scrollbar if dual column

[Zsombor Egri]

Sorry, UX, this doesn't solve the proper aiming on the
AdaptivePageLayout column divider.

Implementing such a functionality is pretty complex and error prone.
First, the order the overlapping components are receiving the touch
events is not predefined, and not even predictable. A touch event is
handled by the topmost instantiated component first, meaning if the
divider is above the Scrollbar, that will get the event first, and will
consume it. This means the Scrollbar below will not even see the event
coming.

In order to implement the event handling above, we could think of the  
following solutions:
1) Create a touch event handler component which would be shared between the 
scrollbar and the divider. The component will then need to be explicitly shared 
between the APL and Scrollbar -> cannot be automated by the toolkit and would 
require to expose some (weird) APIs for both Scrollbar/Scrollview and APL, and 
app developers would need to bind these two components manually.
2) make sure the Scrollview is parented so that is always going to be above the 
APL divider, in this way it can get the touch events prior to the APL divider. 
Then Scrollbar should consume vertical touch drags only, and APL divider the 
horizontal ones, but neither of these should consume the touch press events. 
This may cause problems as the touch events will be forwarded to the flickable 
component under the scrollbar, and no further touch events will be handled.

I was thinking more on a touch grabber spot presence on the APL divider,
and the touch events should be grabbed only when that spot is aimed.

BUT, we still have the mouse interaction, which had not been addressed
by UX at all. So I'm moving back the UX share to In Progress, until we
get a proper solution for both input use cases.

** Changed in: ubuntu-ux
   Status: Fix Committed => In Progress

-- 
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/1545118

Title:
  [AdaptivePageLayout] can't easily grab scrollbar if dual column

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  If you have an app that uses AdaptivePageLayout and supports 2
  columns, if there is a scrollbar in the first column, it's very
  difficult to grab it with your mouse because when you get close to it,
  you get the horizontal arrows showing to allow resizing of the panels
  in the multi-column layout.

  You can try this with messaging-app in silo 30 (soon to land)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1576607] Re: Need public documentation for customizing Button with StyleHints

[Zsombor Egri]

Not every component has a style API, and not every component will have
style API. Ubuntu.Components.Styles contains only those APIs which are
stable and are needed. Checkbox will not have style API for instance
unless the component would need special property presence in the style.

-- 
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/1576607

Title:
  Need public documentation for customizing Button with StyleHints

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Currently, all of the available Ubuntu.Components.Styles elements are
  listed at:

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.5/Ubuntu.Components.Styles/

  This is not a complete list.  There is a more complete list at the
  source tree:

  http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  toolkit/trunk/files/head:/src/Ubuntu/Components/Themes/Ambiance/1.3

  For example, ButtonStyle is not documented though it is implemented.

  Thanks & best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1576607/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1576515] Re: Button style API is not defined, example codes from tutorial are broken

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: High => Medium

-- 
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/1576515

Title:
  Button style API is not defined, example codes from tutorial are
  broken

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I just copied the code snippet at
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.5/Ubuntu.Components.StyledItem/,
  I get the error like http://paste.ubuntu.com/16123241/

  QML debugging is enabled. Only use this in a safe environment.
  qml: Page_QMLTYPE_17(0xa86bd0)"test page": In Ubuntu.Components 1.3, the use 
of Page.title, Page.flickable and Page.head is deprecated. Use Page.header and 
the PageHeader component instead.
  file:///usr/ubuntu-sdk-dev/qml/Ubuntu/Components/1.3/Button.qml:108:25: 
Unable to assign [undefined] to QFont
  file:///usr/ubuntu-sdk-dev/qml/Ubuntu/Components/1.3/Button.qml:103:33: 
Unable to assign [undefined] to QQuickGradient*
  file:///usr/ubuntu-sdk-dev/qml/Ubuntu/Components/1.3/Button.qml:92:27: Unable 
to assign [undefined] to QColor

  The example code is at https://github.com/liu-xiao-guo/style

  The code snippet at the link
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/UbuntuUserInterfaceToolkit
  .ubuntu-theming-styles/ also has the same problem.

  Button {
  id: button
  style: Rectangle {
  implicitWidth: units.gu(12)
  implicitHeight: units.gu(5)
  color: styledItem.color
  border {
  width: units.dp(1)
  color: styledItem.strokeColor
  }
  Label {
  text: styledItem.text
  font: styledItem.font
  }
  }
  }

  Thanks & best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1576515/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1576515] Re: Button style API is not defined, example codes from tutorial are broken

[Zsombor Egri]

** Summary changed:

- Button style is not working
+ Button style API is not defined, example codes from tutorial are broken

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

-- 
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/1576515

Title:
  Button style API is not defined, example codes from tutorial are
  broken

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I just copied the code snippet at
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.5/Ubuntu.Components.StyledItem/,
  I get the error like http://paste.ubuntu.com/16123241/

  QML debugging is enabled. Only use this in a safe environment.
  qml: Page_QMLTYPE_17(0xa86bd0)"test page": In Ubuntu.Components 1.3, the use 
of Page.title, Page.flickable and Page.head is deprecated. Use Page.header and 
the PageHeader component instead.
  file:///usr/ubuntu-sdk-dev/qml/Ubuntu/Components/1.3/Button.qml:108:25: 
Unable to assign [undefined] to QFont
  file:///usr/ubuntu-sdk-dev/qml/Ubuntu/Components/1.3/Button.qml:103:33: 
Unable to assign [undefined] to QQuickGradient*
  file:///usr/ubuntu-sdk-dev/qml/Ubuntu/Components/1.3/Button.qml:92:27: Unable 
to assign [undefined] to QColor

  The example code is at https://github.com/liu-xiao-guo/style

  Thanks & best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1576515/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514860] Re: OptionSelector does not work with keyboard

[Zsombor Egri]

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => In Progress

-- 
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/1514860

Title:
  OptionSelector does not work with keyboard

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Triaged

Bug description:
  OptionSelector does not fully work with only keyboard. There is no way
  to select a option on OptionSelector using only the keyboard.

  Pressing the arrows does not navigate on the options. And it does not
  have any visual feedback that it contains focus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514860/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558106] Re: Invalid use of palette apparent with new SDK

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

** Changed in: canonical-devices-system-image
   Status: Confirmed => Invalid

-- 
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/1558106

Title:
   Invalid use of palette apparent with new SDK

Status in Canonical System Image:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntuone-credentials package in Ubuntu:
  Invalid

Bug description:
  The U1 login form uses the wrong palette values for text (which
  becomes apparent with new UITK), see screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558106/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1575060] Re: APL divider goes on top of column content

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1575060

Title:
  APL divider goes on top of column content

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The APL divider will hide part of the column content. To work around
  this and to avoid the right edge of the focus frame for uclistitem to
  be hidden by the APL divider, uclistitem has this code on line 1143:
  rect -= QMarginsF(0, 0, UCUnits::instance()->dp(1), 0);

  That causes a bug with the sections  focus frame (which is the
  ListItem focus frame), there is a 'gap' of 1 pixel wide on the right-
  hand side of the focus frame which looks wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1575060/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1563440] Re: Add ContentHub text import option to text field context menu

[Zsombor Egri]

This needs UX input.

** Also affects: ubuntu-ui-toolkit
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-ui-toolkit

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Christian Dywan (kalikiana)

-- 
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/1563440

Title:
  Add ContentHub text import option to text field context menu

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  It would be nice to have an "Import" option to a text field's context
  menu, next to cut/copy/paste, that will open a ContentPeerPicker for
  apps that can share Text.

  Currently you can open another app, and copy text from it if it
  supports copying, then paste it into the text field. But we have a
  nice ContentHub service that supports sharing chunks of text, and it
  would streamline the user experience if we could enable this by
  default for text inputs.

  Bonus points if we could send some context along with the import
  request, such as what app or website it's going to, but I don't think
  the ContentHub API supports that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1563440/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1320860] Re: Section header should not go under the page header

[Zsombor Egri]

Or simply use the PageHeader in ListView's header.

-- 
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/1320860

Title:
  Section header should not go under the page header

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Listview header should stick to header, like in unity8.

  Probably will be solved in UbuntuListView, or by contributing unity8
  changes upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1320860/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1573027] [NEW] Palette color setup not optimal, can cause performance problems when loading the theme

[Zsombor Egri]

Public bug reported:

Separate string checking for each property that needs a different value
is slow.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Pierre Bertet (bpierre)
 Status: Fix Committed

** Branch linked: lp:~bpierre/ubuntu-ui-toolkit/palette-colors-
optimization

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
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/1573027

Title:
  Palette color setup not optimal, can cause performance problems when
  loading the theme

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Separate string checking for each property that needs a different
  value is slow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1573027/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1572525] Re: [regression] Double header height is set as flickable topMargin

[Zsombor Egri]

Alberto, may I ask what is the reason you are settjng the ListView
delegate's flickable the one to control the header  movement? That seems
to be a bit of a bad idea tbh...

-- 
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/1572525

Title:
  [regression] Double header height is set as flickable topMargin

Status in Canonical System Image:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Th attached test application works fine under qml-module-ubuntu-
  components 1.3.1918+16.04.20160404-0ubuntu3 but breaks with the latest
  1.3.1938+16.04.20160416. At a first examination, I believe that the
  change which cause the regression is this one:

  https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/invisible-
  header-topmargin/+merge/290659

  Run the attached test case with QML scene. You can scroll the view
  horizontally to see the other model items. Under the old version of
  the toolkit, all items have their page headers correctly aligned; with
  the new version, an extra spacing is added below the header.

  I found this bug while testing my ttrss app in rc-proposed; please
  don't let this UITK version reach our users, as more apps might be
  affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1572525/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553090] Re: Binding loops in implicitWidth with OTA 10 landing

[Zsombor Egri]

@tim, does the Icon derive from AbstractButton? :D

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

-- 
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/1553090

Title:
  Binding loops in implicitWidth with OTA 10 landing

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  In Progress

Bug description:
  The simple code

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  AbstractButton {
  implicitWidth: childrenRect.width
  implicitHeight: childrenRect.height
  Label {
  id: titleLabel
  text: "HOLA CARACOLA"
  }
  }

  is giving

  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitWidth"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitWidth"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitHeight"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitWidth"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitHeight"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitWidth"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitHeight"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitWidth"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitWidth"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitHeight"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitWidth"
  file:///home/tsdgeos_work/test/1.qml:4:1: QML AbstractButton: Binding loop 
detected for property "implicitHeight"

  with the OTA 10 landing as of today.

  This works fine without that landing and i think it's valid code that
  should not be giving out warnings like this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553090/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558106] Re: Invalid use of palette apparent with new SDK

[Zsombor Egri]

Could you please update the import to 1.3? The version detection may be
screwed if you import 0.1 versions, and we cannot do anything about it
unfortunately. There is no official way to detect from a component in
what version is imported, what we do is a workaround which may break any
time. Also, do not mix the import version if UITK and its submodules!
Import consistently!

-- 
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/1558106

Title:
   Invalid use of palette apparent with new SDK

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Invalid

Bug description:
  The U1 login form uses the wrong palette values for text (which
  becomes apparent with new UITK), see screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558106/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1563211] Re: Clicking on a listitem doen't select the item

[Zsombor Egri]

maybe we add a property to auto-select the currentIndex... we must check
whether this makes sense, we must check the performance drawbacks of
having this feature there.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

-- 
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/1563211

Title:
  Clicking on a listitem doen't select the item

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  clicking on a list item doens't set the item as the current index by
  default. This is very problematic when actions are used and the list
  item is right clicked as the user can selected the context menu but
  the action is performed on the currentindex which is not the item that
  was selected.

  This can be overcome by adding ListView.currentIndex = index to every
  action but its seem that allowing the item to be selected by default
  would be much cleaner.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1563211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1507339] Re: Small gap between listitem and first trailing action

[Zsombor Egri]

Could you please check it again? Is it still valid?

-- 
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/1507339

Title:
  Small gap between listitem and first trailing action

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In the example app [0] when swiping the listitem to the left, you can
  see a very small grey between the green (listitem) and blue (listitem
  action).

  It was expected that there would be no gap between the end of the
  listitem and start of the listitem actions

  0 - http://pastebin.ubuntu.com/12846246/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1507339/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1563262] Re: AdaptivePageLayout ignores column's minimumWidth if MainView defaults to one column layout

[Zsombor Egri]

** Summary changed:

- AdvancedPageLayout ignores column's minimumWidth if MainView defaults to one 
column layout
+ AdaptivePageLayout ignores column's minimumWidth if MainView defaults to one 
column layout

-- 
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/1563262

Title:
  AdaptivePageLayout ignores column's minimumWidth if MainView defaults
  to one column layout

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  r1905

  Description:
  When MainView starts in 1 column mode, AdvancedPageLayout ignores left 
column's minimumWidth until the window is manually resized to trigger a switch 
to dual panel mode and then back to one.

  How to reproduce:
  1) Grab the UITK code, we're going to modify the UITK gallery
  2) Change the size of ubuntu-ui-toolkit-gallery.qml MainView to units.gu(30)
  3) Run the gallery

  Expected outcome: 
  The chevron on the right side of the listitems should be visible, because 
minimumWidth of the left panel is currently set to units.gu(30)

  Actual outcome:
  The left panel minimumWidth is ignored and seems to default to 40GU, until 
you manually resize the window to trigger a switch to 2 columns and then shrink 
it to change back to the 1 column layout. At this point you'll be able to 
resize the window to be 30GU wide and the chevrons will still be visible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1563262/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1097728] Re: [ListItems] too many different ListItems that are not flexible enough

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid)
   Status: New => Fix Released

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
   Status: New => Fix Released

-- 
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/1097728

Title:
  [ListItems] too many different ListItems that are not flexible enough

Status in Ubuntu UI Toolkit:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Vivid:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Fix Released

Bug description:
  Feedback from Michael Zanetti:

  "Maybe I just missed the one i wanted. But in general I have the
  feeling there are to many different ones and they are not flexible
  enough.

  For example I have one ListView which I use for different models. The
  delegates always have an image and a label, sometimes also a subtitle.
  Using only the available Delegates I could use either a single line
  delegate or a two line delegate. Using the two line delegate doesn't
  center the text vertically if the model doesn't provide a subtitle."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1097728/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1380766] Re: revert listitem dividers to previous (no margins)

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid)
   Status: New => Fix Released

-- 
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/1380766

Title:
  revert listitem dividers to previous (no margins)

Status in Canonical System Image:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Vivid:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Fix Released

Bug description:
  2gu margin was added to the left and right of listitem dividers.

  However this is causing issues with a large number of apps. For RTM
  let's revert back to previous (no left/right margins on listitem
  dividers) and after that we can explore the issues again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1380766/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567840] Re: tst_datepicker generates segfault

[Zsombor Egri]

Actually 1.2 has a QML component, so my sensing area exclusion doesn't
have any effect on 1.2.

-- 
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/1567840

Title:
  tst_datepicker generates segfault

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On my amd64 xenial laptop:

  tim@tim-mbp:~/dev/ubuntu-ui-toolkit/m/datepicker-
  segfault/tests/unit_x11/tst_components$ qmltestrunner -import
  ../../../qml/ -input tst_datepicker.qml

  * Start testing of qmltestrunner *
  Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.3.1 20160225)
  PASS   : qmltestrunner::DatePickerAPI::initTestCase()
  QWARN  : qmltestrunner::DatePickerAPI::test_0_date() [PERFORMANCE]: Last 
frame took 43 ms to render.
  PASS   : qmltestrunner::DatePickerAPI::test_0_date()
  PASS   : qmltestrunner::DatePickerAPI::test_0_locale()
  PASS   : qmltestrunner::DatePickerAPI::test_0_minimum_maximum()
  PASS   : qmltestrunner::DatePickerAPI::test_0_mode()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDate()
  QWARN  : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth() 
file:///home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/qml/Ubuntu/Components/Pickers/1.2/DatePicker.qml:374:5:
 QML DayModel: Binding loop detected for property "date"
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeLocale()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumAfterDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumBeforeDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeH()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHMS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeHS() cannot set mode 
to Hours|Minutes
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(194)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMinute()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled() unhandled 
mode flag should not pass
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(254)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeY()
  Segmentation fault (core dumped)

  Also segfaults on jenkins, blocking all merges, see
  https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/424/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1567840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567840] Re: tst_datepicker generates segfault

[Zsombor Egri]

Oh, and Tim, there is no Ubuntu.Tests 1.2 in the system, only 1.0 or
1.3.

-- 
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/1567840

Title:
  tst_datepicker generates segfault

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On my amd64 xenial laptop:

  tim@tim-mbp:~/dev/ubuntu-ui-toolkit/m/datepicker-
  segfault/tests/unit_x11/tst_components$ qmltestrunner -import
  ../../../qml/ -input tst_datepicker.qml

  * Start testing of qmltestrunner *
  Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.3.1 20160225)
  PASS   : qmltestrunner::DatePickerAPI::initTestCase()
  QWARN  : qmltestrunner::DatePickerAPI::test_0_date() [PERFORMANCE]: Last 
frame took 43 ms to render.
  PASS   : qmltestrunner::DatePickerAPI::test_0_date()
  PASS   : qmltestrunner::DatePickerAPI::test_0_locale()
  PASS   : qmltestrunner::DatePickerAPI::test_0_minimum_maximum()
  PASS   : qmltestrunner::DatePickerAPI::test_0_mode()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDate()
  QWARN  : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth() 
file:///home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/qml/Ubuntu/Components/Pickers/1.2/DatePicker.qml:374:5:
 QML DayModel: Binding loop detected for property "date"
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeLocale()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumAfterDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumBeforeDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeH()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHMS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeHS() cannot set mode 
to Hours|Minutes
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(194)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMinute()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled() unhandled 
mode flag should not pass
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(254)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeY()
  Segmentation fault (core dumped)

  Also segfaults on jenkins, blocking all merges, see
  https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/424/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1567840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567840] Re: tst_datepicker generates segfault

[Zsombor Egri]

I dunno how you identified the crash to happen at pickerItemChanged
signal. I refactored the code to have one single pickerItem on the
Picker level. So no pickerItemChange should happen. The crash happens at
the test loading phase, when Loader loads the text component. I've
excluded the sensing area logic from AbstractButton, which previously
caused problems, but we still have crashes.

-- 
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/1567840

Title:
  tst_datepicker generates segfault

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On my amd64 xenial laptop:

  tim@tim-mbp:~/dev/ubuntu-ui-toolkit/m/datepicker-
  segfault/tests/unit_x11/tst_components$ qmltestrunner -import
  ../../../qml/ -input tst_datepicker.qml

  * Start testing of qmltestrunner *
  Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.3.1 20160225)
  PASS   : qmltestrunner::DatePickerAPI::initTestCase()
  QWARN  : qmltestrunner::DatePickerAPI::test_0_date() [PERFORMANCE]: Last 
frame took 43 ms to render.
  PASS   : qmltestrunner::DatePickerAPI::test_0_date()
  PASS   : qmltestrunner::DatePickerAPI::test_0_locale()
  PASS   : qmltestrunner::DatePickerAPI::test_0_minimum_maximum()
  PASS   : qmltestrunner::DatePickerAPI::test_0_mode()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDate()
  QWARN  : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth() 
file:///home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/qml/Ubuntu/Components/Pickers/1.2/DatePicker.qml:374:5:
 QML DayModel: Binding loop detected for property "date"
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeLocale()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumAfterDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumBeforeDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeH()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHMS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeHS() cannot set mode 
to Hours|Minutes
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(194)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMinute()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled() unhandled 
mode flag should not pass
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(254)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeY()
  Segmentation fault (core dumped)

  Also segfaults on jenkins, blocking all merges, see
  https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/424/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1567840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1567840] Re: tst_datepicker generates segfault

[Zsombor Egri]

For me the segfault moves to a later test if I do the changes in #4.

-- 
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/1567840

Title:
  tst_datepicker generates segfault

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On my amd64 xenial laptop:

  tim@tim-mbp:~/dev/ubuntu-ui-toolkit/m/datepicker-
  segfault/tests/unit_x11/tst_components$ qmltestrunner -import
  ../../../qml/ -input tst_datepicker.qml

  * Start testing of qmltestrunner *
  Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.3.1 20160225)
  PASS   : qmltestrunner::DatePickerAPI::initTestCase()
  QWARN  : qmltestrunner::DatePickerAPI::test_0_date() [PERFORMANCE]: Last 
frame took 43 ms to render.
  PASS   : qmltestrunner::DatePickerAPI::test_0_date()
  PASS   : qmltestrunner::DatePickerAPI::test_0_locale()
  PASS   : qmltestrunner::DatePickerAPI::test_0_minimum_maximum()
  PASS   : qmltestrunner::DatePickerAPI::test_0_mode()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDate()
  QWARN  : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth() 
file:///home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/qml/Ubuntu/Components/Pickers/1.2/DatePicker.qml:374:5:
 QML DayModel: Binding loop detected for property "date"
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeLocale()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumAfterDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumBeforeDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeH()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHMS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeHS() cannot set mode 
to Hours|Minutes
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(194)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMinute()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled() unhandled 
mode flag should not pass
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(254)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeY()
  Segmentation fault (core dumped)

  Also segfaults on jenkins, blocking all merges, see
  https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/424/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1567840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp