Therefore, it can be debugged and modified in the same way of Firefox if you know how to debug Firefox.
XUL applications are consisted of several XUL, JavaScript, and CSS files.
They are archived in a Jar file so Fennec also has two jar files in fennec/chrome/
The en-US.jar has localization information, the chrome.jar has Fennec front-end code.
If you want to modify them,
1) Extract the chrome.jar in the current path
2) Modify the chrome.manifest as follows
override chrome://global/skin/about.css chrome://browser/skin/about.cssIn order to display variable value as well as simple debug message information of JavaScipt in a system console, you can use the dump function. Before using this command, you have to enable browser dump preference in terms of typing about:config in the URL bar.
skin browser classic/1.0 content/..
content branding content/branding/
content firstrun content/ contentaccessible=yes
content browser content/
browser.dom.window.dump.enabled=true
There is an example of using dump() at the startup() funciton in the browser.js
startup: function() {
var self = this;
dump("begin startup\n");
let container = document.getElementById("tile-container");
...
The dump function works well in Linux system, but
It works well in Visual Studio. I could see debug messages in the output box of Visual Studio using latest build of Fennec.
References
Posts
