Pale Moon forum

Why can't edit them?

zcyzcy88 wrote:Why can't edit them?

Because it's not a storage editor. It's a storage viewer. Devtools are present to help you develop and debug site code; being able to view storage will help writing proper site code. Editing storage values manually won't help, and as such it's a viewer.

Moonchild wrote:Editing storage values manually won't help, and as such it's a viewer.

Well, but DevTools is not only for web-page developers, also for power users / hackers / add-on developers.
It is needed and helpful when I sometime need hack, and I don't want to use Firebug or other add-ons.

By the way, is it difficult to implement this feature?

used by != created for. Extension devs normally won't need this on-the-fly data editing either, because it's still not going to fix their scripting

So that leaves... power users who want to hack data?
Can you give an example where this is both helpful and needed?

PS: "I don't want to use extensions" is not an argument when using a browser that is, at its core, lean on purpose so people can extend it as they need.

My case:
I can edit via console, but can't edit httpOnly cookies. Other case:
- Try to delete part of cookies to test how server handle it (test server software)
- Some web-app use localStorage to save setting, I want copy it to backup, paste it to restore

And, further according to your logic, DOM Inspector should also not editable. (double standard)

zcyzcy88 wrote:- Try to delete part of cookies to test how server handle it (test server software)
- Some web-app use localStorage to save setting, I want copy it to backup, paste it to restore

If you want to play with requests and test server side handling, it might be better to use an application suited for that, e.g. Postman - https://www.getpostman.com/
You can always export a request as cURL from Pale Moon, import it in Postman and play as you wish.

zcyzcy88 wrote:And, further according to your logic, DOM Inspector should also not editable. (double standard)

Incorrect. Editing the DOM and CSS is important to be able to see the immediate layout results in the web page. Not so for cookies and storage.

Please stop making every "wontfix" a fight. There are good reasons why certain things are implemented a certain way. If you want to offer enhancements to them is one thing, making demands to cater to your specific workflow is another. See viewtopic.php?f=13&t=5647

zcyzcy88 wrote:Why can't edit them?

...and because no one added it to Pale Moon.

See also:
https://bugzilla.mozilla.org/show_bug.cgi?id=1031192

The reason & case is said before.
It is even OK if Pale Moon have no build-in DevTools, but a non-editable DevTools is really out of common knowledge.

If have no time to implement, "backlog" instead of "wontfix".

[hr][/hr]

GMforker wrote: ...and because no one added it to Pale Moon.
See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1031192

Good "reason". Surprise.

Since the DevTools have been given a refresh (followed the upstream), this case is solved.