openSUSE admin

Copy to clipboard doesn't work either, and the page is prohibiting selection to attempt copy & paste elsewhere to see the unformatted plain text original in plain text format for it to be at all comprehensible. The page source is also useless, littered with markup.

mrmazda wrote:

IIRC, it used to always work before the recent pastes.opensuse.org overhaul.
https://paste.opensuse.org/pastes/7f631951c1b8 is just a sample of failure. Based on sampling https://paste.opensuse.org/pastes it appears
RAW links to pasted images open as expected in same tab, but not to plain text pastes, such as zypper lr output from *c1b8 that wants to
open a different web browser than the one I use for openSUSE QA activities.

In my firefox, the txt file is just automatically downloaded and saved.

Copy to clipboard doesn't work either,

"Copy link to clipboard" works for me, although it is just a copy of the paste.o.o URL. Not very useful.

and the page is prohibiting selection to attempt copy & paste elsewhere

Here select worked just fine, although I had to right click and hit "Copy" to actually get a copy.

to see the unformatted plain text original in plain text format for it to be at all comprehensible.

Apart from having to scroll to the right to see the repo URLs, I had no problem with seeing the plain text format.

The page source is also useless, littered with markup.

Feel free to submit a PR.

Here in latest SeaMonkey, lastest Falkon and latest Palemoon the RAW links produce popups for opening in another application.

I don't know what PR is.

mrmazda wrote:

Here in latest SeaMonkey, lastest Falkon and latest Palemoon the RAW links produce popups for opening in another application.

That suggests something might be wrong with the MIME type. Using wget, the header looks like this:

Connecting to s3.opensuse-project.net (s3.opensuse-project.net)|2001:67c:2178:8::16|:443... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 200 OK
  date: Wed, 22 Mar 2023 19:16:16 GMT
  content-type: text/plain
  content-length: 6093
  accept-ranges: bytes
  content-disposition: attachment; filename="3d38969d16b814edcfcfc082cc9965cf.txt"; filename*=UTF-8''3d38969d16b814edcfcfc082cc9965cf.txt
  content-security-policy: block-all-mixed-content
  etag: "ef440f75f680d12c7cf0fa4309ecd2ac"
  last-modified: Wed, 22 Mar 2023 13:09:15 GMT
  no-gzip-compression: true
  vary: Origin
  vary: Accept-Encoding
  x-amz-request-id: 174ED3CA18175171
  x-frame-options: SAMEORIGIN
  x-xss-protection: 1; mode=block
  x-content-type-options: nosniff
  referrer-policy: no-referrer-when-downgrade
  strict-transport-security: max-age=15768000
Length: 6093 (6.0K) [text/plain]

"text/plain" is of course okay, but that content-disposition does look a bit odd. Multiple filenames?

I don't know what PR is.

If you're unhappy with how something is implemented, you fix it and submit a pull request, a PR.

Happening again on linked pastes from https://forums.opensuse.org/t/no-hdmi-out-on-asus-computer/165646 with current SeaMonkey 2.53.16.

mrmazda wrote:

Happening again on linked pastes from https://forums.opensuse.org/t/no-hdmi-out-on-asus-computer/165646 with current SeaMonkey 2.53.16.

Unable to reproduce with Firefox - all four links are downloaded, with MIME-type "text/x-log" which corresponds to the .log extension.
With Chromium, the files are just shown as text. The handling of that MIME type seems to vary, but it might also be dependent on the content-disposition:

content-disposition: inline; filename="G75VW_temp_001-a.log"; filename*=UTF-8''G75VW_temp_001-a.log

"disposition inline" sounds wrong to me, for the raw link. Seems it ought to be "attachment". I don't know about the format of that "filename*" argument, but a quick check of RFC5987 suggests it is correct.

another that SeaMonkey wants Kate to open:
https://paste.opensuse.org/pastes/cff1b91c21be

mrmazda wrote:

another that SeaMonkey wants Kate to open:
https://paste.opensuse.org/pastes/cff1b91c21be

Again, it's a log file Xorg-0.log- content-type text/x-log. With FF, it was just downloaded. With Chrome, it is rendered in the browser. For a text type, the latter seems most appropriate. I guess your Seamonkey is configured to use Kate for text files.