Firefox Profiler UI adds support for a `hexadecimal` marker schema field format. A field declared with `format: "hexadecimal"` takes an integer value and renders it in hex with a `0x` prefix, so producers no longer need to pre-format the value into a string. Today, [HostResolverMarker](https://searchfox.org/firefox-main/source/netwerk/dns/nsHostRecord.cpp#47) stores its 32-bit flags as a pre-formatted hex string. We should instead write the raw integer with `format: "hexadecimal"` and let the profiler format it. This should be implemented immediately after the [frontend change PR](https://github.com/firefox-devtools/profiler/pull/6197).
Bug 2056208 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Firefox Profiler UI adds support for a `hexadecimal` marker schema field format. A field declared with `format: "hexadecimal"` takes an integer value and renders it in hex with a `0x` prefix, so producers no longer need to pre-format the value into a string. Today, [HostResolverMarker](https://searchfox.org/firefox-main/source/netwerk/dns/nsHostRecord.cpp#47) stores its 32-bit flags as a pre-formatted hex string. We should instead write the raw integer with `format: "hexadecimal"` and let the profiler format it. Note that the hexadecimal format first needs to be implemented. This should be implemented immediately after the [frontend change PR](https://github.com/firefox-devtools/profiler/pull/6197).