| Summary: | Long URIs cause bug information to be rendered off-page | ||
|---|---|---|---|
| Product: | [Websites] bugs.kde.org | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
| Component: | general | Assignee: | KDE sysadmins <sysadmin> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | nate, sheedy |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| URL: | https://unix.stackexchange.com/revisions/777040/1#:~:text=the%20user%20cannot%20retroactively%20select%20it%2C%20because%20it%20doesn't%20appear%20in%20the%20user%20list%20(the%20user%20you%20see%20is%20my%20user%2C%20not%20the%20superuser). | ||
| Latest Commit: | https://invent.kde.org/websites/bugs-kde-org/-/commit/309d942fdb3425890abc61c2189b9b45570b7918 | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: |
Depiction of the problem.
Demonstration of the problem. |
||
|
Description
Roke Julian Lockhart Beedell
2024-05-23 22:12:24 UTC
Created attachment 169758 [details]
Demonstration of the problem.
We can probably fix this in the CSS, but regardless, please don't put silly URLs like that in the text field. The ":text=" part is completely unnecessary. Git commit 309d942fdb3425890abc61c2189b9b45570b7918 by Ben Cooksley. Committed on 24/05/2024 at 10:50. Pushed by bcooksley into branch 'kde-5.0'. Fix display of Long URIs on show_bug.cgi. M +8 -0 skins/standard/additions/global.css https://invent.kde.org/websites/bugs-kde-org/-/commit/309d942fdb3425890abc61c2189b9b45570b7918 (In reply to Nate Graham from comment #2) I won't do it again, but I certainly didn't do it thinking it was useless - a text fragment can encode text, meaning that when the original page becomes unavailable, the important content remains referred to. If the link becomes inactive or gets broken, encoding a long random string of text in its URL isn't in any way a substitute for the content that's now inaccessible. (In reply to Nate Graham from comment #5) Indeed, reading something like https://developer.mozilla.org/en-US/docs/Web/Text_fragments#syntax would appear to demonstrate that. Fragments with start and end parameters are how most function, because they are more efficient to send. However, that's not the sole format available - see https://developer.mozilla.org/en-US/docs/Web/Text_fragments#simple_text_fragment_with_textstart Just stop doing it, it doesn't help anything for anyone. (In reply to Nate Graham from comment #7) I've already said I shall. You needn't reiterate. Thanks. Then stop explaining why you *did* do it in the past. It isn't relevant. You are wasting everyone's time. (In reply to Nate Graham from comment #9) I'm confused. You responded at https://bugs.kde.org/show_bug.cgi?id=487450#c5 after the issue was marked as RESOLVED to discuss this topic - why is me responding to you problematic? Surely you wouldn't have said anything unless you wanted to discuss it...? (In reply to Roke Julian Lockhart Beedell from comment #10) Regardless, you really needn't be so aggressive. It won't make for a pleasant conversation for either of us. Your constant demands for explanation about *everything* are infuriating--you being a time vampire is what makes pleasant conversation impossible. Maybe you don't realize this behavior is infuriating, but it is. Stop it. (In reply to Nate Graham from comment #12) I didn't ask for an explanation of anything. I've just read our entire conversation to verify that. The sole thing I've done in this issue is report a bug, and provide an explanation of how I discovered it. I'm glad to hear any criticisms you have of my personality, but they're best directed at me outside of this avenue, and I would prefer them to at least be substantiated. |