** No longer affects: notify-osd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/331019
Title:
notifications do not display content if not supported markup tags are
used (aka a href=... links)
To
** Changed in: notify-osd
Status: Fix Committed = Fix Released
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package notify-osd - 0.9ubuntu2
---
notify-osd (0.9ubuntu2) jaunty; urgency=low
* Merge bug fixes from trunk (r219):
- Added max. limit of 10 lines for message-body text.
- 3-line wrapping for summary text.
- capability truncation now
I've commited a fix, that will pass any text as is, if the markup-filter
fails.
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug notification because you are a member of Ubuntu
I commited a fix that will pass such text as-is, thus the bubble will
not be empty.
** Changed in: notify-osd
Status: Triaged = Fix Committed
** Changed in: notify-osd (Ubuntu Jaunty)
Status: Triaged = Fix Committed
--
notifications do not display content if not supported markup
On Wed, Feb 25, 2009 at 12:37:49PM -, David Barth wrote:
Assigned to the upstream project. This is really not a packaging bug.
I don't think we should remove the text of the link. We should render it
as plain text.
my suggestion was to render it as plain text with _underscore_
attribute.
I think underlining links would suggest that they are clickable when
they are not.
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug notification because you are a member of Ubuntu
I don't think displaying the hyperlink with the underscore is a good
idea. It will suggest that it's clickable, and that's misleading.
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this
On Thu, Feb 19, 2009 at 06:30:33PM -, Mat Tomaszewski wrote:
Alexander, I strongly disagree - once we make one exception to You cannot
interact with notification bubbles rule it will cause a whole bunch of other
exceptions to follow, and the whole concept of non-intrusive notifications
MPT, you got there first, *again*.
:)
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Alexander, it seems like I was very sleepy/partly unconscious and
clearly misread your comment. You're 100% right, what I wrote there
doesn't actually make much sense :)
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
** Tags added: jaunty-uif
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Assigned to the upstream project. This is really not a packaging bug.
I don't think we should remove the text of the link. We should render it
as plain text.
** Also affects: notify-osd
Importance: Undecided
Status: New
** Changed in: notify-osd
Importance: Undecided = Medium
** Description changed:
- Binary package hint: alsdorf
-
- Reproduce:
- 1. notify-send Test 'before a href=http://www.nothing.tld;link/a
after'
+ 1. notify-send Test 'before a href=http://www.nothing.tld;link/a
+ after'
Result:
- notification pops up only showing the title Test; the
** Tags added: dxteam notifications
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Dominic's temporary fix works for me.
http://bazaar.launchpad.net/~gwibber-committers/gwibber/trunk/revision/247
displays plain text instead of a blank box.
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
bumping importance. This is really loss of displayed content without any
fallback available.
** Changed in: notify-osd (Ubuntu)
Importance: Undecided = High
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
Suggesting to get this fixed till beta.
** Changed in: notify-osd (Ubuntu Jaunty)
Target: None = ubuntu-9.04-beta
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug
Nobody is asking for an exception though.
But notify-osd should 'do the right thing' by displaying notifications
exactly how they displayed before, but instead of processing and
applying markup that allows interactions, they should simply throw that
markup away.
What we should not have is 'if
Dominic, Alexander, yes of course it should display plain text instead
of an empty box.
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug notification because you are a member of
That is by design. A link implies being able to click on it, but the new
jaunty notification spec does not allow notifications to be clickable.
So the app doing that needs to be patched. A more indepth explanation of
the rationale behind this ui-design decision is in spec. I'll post the
link as
not sure I agree with the reason for this bug being marked as invalid
it might be 'by design' to now not display clickable links, but surely
it is not correct function to display a blank box if the message
contained an a href... link? you are then asking every single app that
previously passed
general rule: be as strict as necessary, but be as polite as possible
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug notification because you are a member of Ubuntu
Bugs, which is
i obviously agree that this is a bug. removing actions is one thing, but
also saying that apps are wrong if they include an optional a href
markup is overly strict and notification daemon can do better.
** Changed in: notify-osd (Ubuntu)
Status: New = Triaged
--
notifications do not
Alexander, I strongly disagree - once we make one exception to You cannot
interact with notification bubbles rule it will cause a whole bunch of other
exceptions to follow, and the whole concept of non-intrusive notifications will
be completely dissolved.
It is a tough compromise, but I feel
** Summary changed:
- notifications does not display content if not supported markup tags are used
(aka a href=... links)
+ notifications do not display content if not supported markup tags are used
(aka a href=... links)
--
notifications do not display content if not supported markup tags
moving alsdorf bugs to new source package: notify-osd
** Changed in: notify-osd (Ubuntu)
Sourcepackagename: alsdorf = notify-osd
--
notifications do not display content if not supported markup tags are used
(aka a href=... links)
https://bugs.launchpad.net/bugs/331019
You received this bug
27 matches
Mail list logo
