Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to the Power Users community on Codidact!

Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.

Post History

50%
+0 −0
Q&A How to resolve an abstracted internal URI in Firefox?

153.0a1-20260606213347 occasionally provides a method to accomplish this, although it may not be deliberate: #!/usr/bin/env pwsh Start-Process firefox-nightly -ArgumentList '-jsdebugger', '--...

posted 3mo ago by Mr. Beedell, Roke Julian Lockhart (RJLB)‭  ·  edited 3mo ago by Mr. Beedell, Roke Julian Lockhart (RJLB)‭

Answer
#2: Post edited by user avatar Mr. Beedell, Roke Julian Lockhart (RJLB)‭ · 2026-06-08T18:47:44Z (3 months ago)
  • `153.0a1-20260606213347` occasionally provides a method to accomplish this, although it may not be deliberate:
  • 1. ~~~pwsh
  • #!/usr/bin/env pwsh
  • Start-Process firefox-nightly -ArgumentList '-jsdebugger', '--new-window', 'view-source:about:neterror?e=nssFailure2&u=https%3A//download.fedoraproject.org/pub/fedora/linux/releases/44/KDE/x86_64/iso/Fedora-KDE-Desktop-Live-44-1.7.x86_64.iso&c=UTF-8&d=%20&a='
  • $Header = '/usr/include/linux/input-event-codes.h'
  • $Control = awk '$1=="#define" && $2=="KEY_LEFTCTRL" {print $3}' $Header
  • $Alt = awk '$1=="#define" && $2=="KEY_LEFTALT" {print $3}' $Header
  • $Shift = awk '$1=="#define" && $2=="KEY_LEFTSHIFT" {print $3}' $Header
  • $I = awk '$1=="#define" && $2=="KEY_I" {print $3}' $Header
  • ydotool key `
  • "$($Control):1" `
  • "$($Alt):1" `
  • "$($Shift):1" `
  • "$($I):1" `
  • "$($I):0" `
  • "$($Shift):0" `
  • "$($Alt):0" `
  • "$($Control):0"
  • ~~~
  • 1. ~~~JS
  • #!/usr/lib/firefox-nightly/browser/omni.ja!/chrome/devtools/content/framework/toolbox.xhtml
  • document.querySelector('#command-button-pick').click();
  • ~~~
  • 1. ~~~JS
  • #!/usr/lib/firefox-nightly/browser/omni.ja!/chrome/browser/content/browser/browser.xhtml
  • document.querySelector('tab.tabbrowser-tab:nth-child(1) > stack:nth-child(1) > hbox:nth-child(2) > vbox:nth-child(3) > label:nth-child(1)').click();
  • ~~~
  • To summarise, inspect the chrome of the relevant error tab's label.
  • `153.0a1-20260606213347` occasionally provides a method to accomplish this, although it may not be deliberate:
  • 1. ~~~pwsh
  • #!/usr/bin/env pwsh
  • Start-Process firefox-nightly -ArgumentList '-jsdebugger', '--new-window', 'view-source:about:neterror?e=nssFailure2&u=https%3A//download.fedoraproject.org/pub/fedora/linux/releases/44/KDE/x86_64/iso/Fedora-KDE-Desktop-Live-44-1.7.x86_64.iso&c=UTF-8&d=%20&a='
  • $Header = '/usr/include/linux/input-event-codes.h'
  • $Control = awk '$1=="#define" && $2=="KEY_LEFTCTRL" {print $3}' $Header
  • $Alt = awk '$1=="#define" && $2=="KEY_LEFTALT" {print $3}' $Header
  • $Shift = awk '$1=="#define" && $2=="KEY_LEFTSHIFT" {print $3}' $Header
  • $I = awk '$1=="#define" && $2=="KEY_I" {print $3}' $Header
  • ydotool key `
  • "$($Control):1" `
  • "$($Alt):1" `
  • "$($Shift):1" `
  • "$($I):1" `
  • "$($I):0" `
  • "$($Shift):0" `
  • "$($Alt):0" `
  • "$($Control):0"
  • ~~~
  • [^1]
  • [^1]: [`discussion.fedoraproject.org/t/193346`](https://discussion.fedoraproject.org/t/the-isos-are-inaccessible/193346)
  • 1. ~~~JS
  • #!/usr/lib/firefox-nightly/browser/omni.ja!/chrome/devtools/content/framework/toolbox.xhtml
  • document.querySelector('#command-button-pick').click();
  • ~~~
  • 1. ~~~JS
  • #!/usr/lib/firefox-nightly/browser/omni.ja!/chrome/browser/content/browser/browser.xhtml
  • document.querySelector('tab.tabbrowser-tab:nth-child(1) > stack:nth-child(1) > hbox:nth-child(2) > vbox:nth-child(3) > label:nth-child(1)').click();
  • ~~~
  • To summarise, inspect the chrome of the relevant error tab's label.
#1: Initial revision by user avatar Mr. Beedell, Roke Julian Lockhart (RJLB)‭ · 2026-06-08T18:47:14Z (3 months ago)
`153.0a1-20260606213347` occasionally provides a method to accomplish this, although it may not be deliberate:

1.	~~~pwsh
	#!/usr/bin/env pwsh
	Start-Process firefox-nightly -ArgumentList '-jsdebugger', '--new-window', 'view-source:about:neterror?e=nssFailure2&u=https%3A//download.fedoraproject.org/pub/fedora/linux/releases/44/KDE/x86_64/iso/Fedora-KDE-Desktop-Live-44-1.7.x86_64.iso&c=UTF-8&d=%20&a='
	$Header = '/usr/include/linux/input-event-codes.h'
	$Control = awk '$1=="#define" && $2=="KEY_LEFTCTRL" {print $3}' $Header
	$Alt = awk '$1=="#define" && $2=="KEY_LEFTALT" {print $3}' $Header
	$Shift = awk '$1=="#define" && $2=="KEY_LEFTSHIFT" {print $3}' $Header
	$I = awk '$1=="#define" && $2=="KEY_I" {print $3}' $Header
	ydotool key `
		"$($Control):1" `
		"$($Alt):1" `
		"$($Shift):1" `
		"$($I):1" `
		"$($I):0" `
		"$($Shift):0" `
		"$($Alt):0" `
		"$($Control):0"
	~~~

1.	~~~JS
	#!/usr/lib/firefox-nightly/browser/omni.ja!/chrome/devtools/content/framework/toolbox.xhtml
	document.querySelector('#command-button-pick').click();
	~~~

1.	~~~JS
	#!/usr/lib/firefox-nightly/browser/omni.ja!/chrome/browser/content/browser/browser.xhtml
	document.querySelector('tab.tabbrowser-tab:nth-child(1) > stack:nth-child(1) > hbox:nth-child(2) > vbox:nth-child(3) > label:nth-child(1)').click();
	~~~

To summarise, inspect the chrome of the relevant error tab's label.