On 4 June 2013 16:33, Tim Tisdall <[email protected]> wrote:

> I tried opening a ticket about this, but I'm not sure how you set up an
> account on https://issues.apache.org/bloodhound .
>

The registration link was hidden under the Apps dropdown:
https://issues.apache.org/bloodhound/register

Once you register you automatically have the permission to create tickets,
edit wiki pages, etc.

The register link is now more obvious in the latest nightly build. It shows
the link next to the Login link at the top:
https://bh-demo1.apache.org/


>
> I'm using 0.5.3 and all the diff views show the titles in the #overview
> section as way over on the far left.  If you look in diff.css you can see
> this:
>
> #overview dt.property {
> font-weight: bold;
> padding-right: .25em;
> position: absolute; /* relies on #content { position: relative } */
> left: 0;
> text-align: right;
> width: 7.75em;
> }
>
> Well, there's no "#content { position: relative }" in the CSS that's loaded
> for bloodhound.  It seems to exist in trac.css which is not loaded.  So, a
> quick fix would be to add that short rule into one of the CSS being loaded
> (such as bloodhound.css).
>
> Here's a link with an example of the problem:
> https://issues.apache.org/bloodhound/ticket/513?action=diff&version=1  (on
> the far left is  "Timestamp", "Author", and "Comment")
>
> - Tim


Thanks for spotting this. Good work.

It looks like this is now fixed on trunk - contrast:
* 0.5.3: https://bh-demo2.apache.org/ticket/100?action=diff&version=1
* trunk:
https://bh-demo1.apache.org/products/%40/ticket/100?action=diff&version=1
(Thanks to Gary (gjm) for the links)

We've recently been discussing the release of 0.6, which will include fixes
such as this. Should be ready soon, Ryan (rjollos) has volunteered to
manage the release and he'll send out emails when it's ready to be tested.

Keep 'em coming! :-)

Cheers,
Joe

-- 
Joachim Dreimann I *User Experience Manager*

WANdisco // *Non-Stop Data*

e. [email protected]
twitter @jdreimann <https://twitter.com/jdreimann>

Reply via email to