Rodney: why is that no longer affecting the click scope? Shouldn't the
scope translate tech error messages? We cannot always rely on the
remote component to do this, e.g. when it comes to network errors.
** Changed in: unity-scope-click (Ubuntu)
Assignee: (unassigned) = Rodney Dawes (dobey)
Thomas, unity-scope-click as an upstream project doesn't have bugs on
LP. They are filed against the package. The no longer affects changes
was simply for that.
Though, I don't think this is an issue any longer, as we don't actually
show any HTTP error messages to the user in the new scope. This
** Changed in: unity-scope-click (Ubuntu)
Assignee: Rodney Dawes (dobey) = (unassigned)
** Tags removed: rls-s-incoming rtm14
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
This bug was filed against the old click scope made with vala; the new
one is not exhibiting this behavior anymore, so let's mark this bug as
Invalid.
If there are any weird error message in the new click scope, please open
new bugs for those and we'll make sure to fix them.
thanks!
** Changed
** Tags added: qa-daily-testing rtm14
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1227100
Title:
Error messages are too technical.
Status in
5 matches
Mail list logo
