requests strings overlap in the html report / details

Hi all,

I came across this issue a few days ago. What is the best solutions for this thing ? The links are extracted from a parsed start page , so we need to have there actual links instead of aliases.



You could use the transform step in the check and chop off the beginning of the string:

Here’s an example, but there’s other alterantives:
.transform(strings =>{ string => string.split(".com")(1)})


thanks for the quick answer. It may work for the short urls like in example , but there are are much longer ones -

and taken in account they are dynamically gathered it is not always possible to make transformation.

The desired behavior is to fix css file to keep the url within bounds and move it on the next line instead of overlapping .


Пʼятниця, 5 квітня 2013 р. 08:19:06 UTC+3 користувач Stéphane Landelle написав:

I might be wrong, but I don't think there's any way to have a css style
"cut" a continuous string containing no spaces.
I see two solutions:

   - cut the long string during reports generation (no very handy)
   - redesign the charts so that the menu can somehow expand without
   breaking everything

Anyhow, contributions welcome [?]


i see it looks very nice on the “GLOBAL” page and then overlap occurs on the “Details” page


Пʼятниця, 5 квітня 2013 р. 12:38:08 UTC+3 користувач Stéphane Landelle написав:

Ah ah? I will have a look ASAP.

PS: don’t bother keeping on anonymizing your snapshots, you failed on the first one 32A.png

It’s because in the global stats, it’s a table, and in the menus, list items. ^^


Here comes the guy in charge, cool!
Make it a table?


Nope absolutely not :wink: better play with css or reduce text before. HTML elements have meaning ^^

Will see what I can do :wink: Is there an issue assigned to me on github ? :smiley:

Truncating the text won’t do: meaningful part could be the end of the text.

Let’s be pragmatical: if you can do it with pure css, great, otherwise, let’s turn it into a table as it seams the only other option. We’re just building reports, not semantic web.

Here’s the issue:


Didn’t know this property of CSS3, it does the trick on .nav .item in style.css#L234