DevTools/Hacking: Difference between revisions

Jump to navigation Jump to search
Update theme URLs
mNo edit summary
(Update theme URLs)
Line 212: Line 212:
Please ensure that any new files are added so their entire source tree path is part of the URL. To do so, the <tt>jar.mn</tt> entry should look like:
Please ensure that any new files are added so their entire source tree path is part of the URL. To do so, the <tt>jar.mn</tt> entry should look like:


     skin/<X> (<X>)
     skin/<X> (themes/<X>)


where <tt><X></tt> is the path to your file after removing the <tt>/devtools/client</tt> prefix.
where <tt><X></tt> is the path to your file after removing the <tt>/devtools/client/themes/</tt> prefix.


Example:
Example:


* File: <tt>/devtools/client/themes/images/add.svg</tt>
* File: <tt>/devtools/client/themes/images/add.svg</tt>
* Entry: <tt>skin/themes/images/add.svg (themes/images/add.svg)</tt>
* Entry: <tt>skin/images/add.svg (themes/images/add.svg)</tt>


=== Usage ===
=== Usage ===


Chrome theme URLs almost match their source tree path, with one difference: the segment <tt>client</tt> is replaced by <tt>skin</tt>. This is a requirement of the <tt>chrome://</tt> protocol handler.
Chrome theme URLs almost match their source tree path, with one difference: the segment <tt>client/themes</tt> is replaced by <tt>skin</tt>. This is a requirement of the <tt>chrome://</tt> protocol handler.


Example:
Example:


* File: <tt>/devtools/client/themes/images/add.svg</tt>
* File: <tt>/devtools/client/themes/images/add.svg</tt>
* Usage: <tt>chrome://devtools/skin/themes/images/add.svg</tt>
* Usage: <tt>chrome://devtools/skin/images/add.svg</tt>


For files within a single tool, consider relative URLs. They're shorter!
For files within a single tool, consider relative URLs. They're shorter!
Confirmed users
177

edits

Navigation menu