-
Notifications
You must be signed in to change notification settings - Fork 183
HAR Viewer provides APIs that can be used to customize viewer's UI. For example, you can remove default application tabs or toolbar buttons that are not necessary for your needs.
The customization can be done within index.php. This file represents the entry point of the HAR Viewer application.
Here is a simplified version of the file:
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>HAR Viewer Test</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body class="harBody">
<div id="content" version="@VERSION@"></div>
<script src="scripts/jquery.js"></script>
<script data-main="scripts/harViewer" src="scripts/require.js"></script>
<link rel="stylesheet" href="css/harViewer.css" type="text/css"/>
</body>
</html>
-
<div id="content">element contains entire HAR Viewer UI -
scripts/jquery.jsincludes JQuery. -
scripts/require.jsincludes RequireJS. The scripts/harViewer module is automatically loaded. This module represents the entire application. -
@VERSION@is dynamically replaced by the current version number during the build process.
It is possible to registers an event listener to the content element and perform various customization of the UI at the right moment. There are following events you can handle.
-
onViewerPreInitFired before the viewer renders itself into the page. -
onViewerInitFired after the viewer is fully initialized and rendered in the page. -
onViewerHARLoadedFired after a HAR file has been appended into the viewer.
See following example that shows how to register a listener.
<body class="harBody">
<div id="content" version="@VERSION@"></div>
<script src="scripts/jquery.js"></script>
<script data-main="scripts/harViewer" src="scripts/require.js"></script>
<script>
$("#content").bind("onViewerPreInit", function(event)
{
// Get application object
var viewer = event.target.repObject;
});
</script>
</body>
Most of the APIs described below require access to the main application object HARView (defined in harViewer.js. There are two ways how to get reference to the object.
Handle an existing event and use passed event object.
$("#content").bind("onViewerPreInit", function(event)
{
// Get application object
var viewer = event.target.repObject;
});
Find the main application element (the container for entire HAR Viewer UI) and use its repObject property. This approach is suitable in cases when handling events is not the right time and you need to use the application object at any time later.
var viewer = document.getElementById("content").repObject;
Some of the application's tabs (such as Home, About, etc.) are not always necessary in production releases. Following example shows how we can remove them.
$("#content").bind("onViewerPreInit", function(event)
{
// Get application object
var viewer = event.target.repObject;
// Remove unnecessary tabs
viewer.removeTab("About");
viewer.removeTab("Schema");
});
In order to make the viewer easier to use for the end user we might want to hide the entire tab bar (the area where tab labels are displayed) and show only preview of HAR logs.
Following example removes all tabs except of Preview and hides the tab bar.
$("#content").bind("onViewerPreInit", function(event)
{
// Get application object
var viewer = event.target.repObject;
// Remove unnecessary tabs
viewer.removeTab("Home");
viewer.removeTab("DOM");
viewer.removeTab("About");
viewer.removeTab("Schema");
// Hide the tab bar
viewer.showTabBar(false);
});
Similarly to tabs, you can also remove existing toolbar buttons. Again, see an example that removes Download and Clear buttons from the Preview tab.
$("#content").bind("onViewerPreInit", function(event)
{
// Get application object
var viewer = event.target.repObject;
// Remove toolbar buttons
var preview = viewer.getTab("Preview");
preview.toolbar.removeButton("download");
preview.toolbar.removeButton("clear");
});
In order to control visibility of a page timeline and statistics you can use following APIs:
$("#content").bind("onViewerPreInit", function(event)
{
// Get application object
var viewer = event.target.repObject;
// Make sure stats and timeline is visible
// to the user by default
var preview = viewer.getTab("Preview");
preview.showStats(true);
preview.showTimeline(true);
});
Available since HAR Viewer 2.0.8
Timings of events related to the page load such as onLoad and DOMContentLoaded events are displayed as vertical lines drawn over network requests. Following example shows how to append new timings coming from HAR custom fields (see Custom Fields in HAR 1.2 spec).
Let's imagine following HAR file snippet (the page.pageTimings object) with one new custom field.
"pageTimings": {
"onContentLoad": 5605,
"onLoad": 6964,
"_onMyEvent": 4000
},
Note that custom fields must start with an underscore
There is a new field called onMyEvent with a corresponding timing value that says when it happened since the page load beginning.
Now we need to register that field within the viewer as follows:
$("#content").bind("onViewerPreInit", function(event)
{
// Get application object
var viewer = event.target.repObject;
// Add custom page timing displayed as a vertical line
// over request in the first phase.
var preview = viewer.getTab("Preview");
preview.addPageTiming({
name: "_onMyEvent",
classes: "onMyEventBar",
description: "A custom page timing"
});
});
-
nameName of the field in HAR file. -
classesOptional CSS class associated with the vertical line. Can be used to e.g. specify a color of the line. The line is green by default. -
descriptionDescription of the timing/event that is displayed in the tooltip.
An example of a custom CSS class that changes the default color:
<style type="text/css">
.onMyEventBar {
background-color: gray;
}
</style>
Available since HAR Viewer 2.0.12
Apart from specifying a HAR file in the URL, you can also load it manually using loadHar method.
Next example shows how to load HAR file from the same domain.
$("#content").bind("onViewerInit", function(event)
{
var viewer = event.target.repObject;
viewer.loadHar(<path-to-har-file>);
});
In case you want to load HARs from different domain you need to use HARP (JSONP) syntax. See another example:
$("#content").bind("onViewerInit", function(event)
{
var viewer = event.target.repObject;
var settings = {jsonp: true};
viewer.loadHar(<path-to-har-file>, settings);
});
If you already have the HAR log object loaded and parsed, you can directly append it using appendPreview method.
$("#content").bind("onViewerInit", function(event)
{
var viewer = event.target.repObject;
var log = <har-file-loaded-and-parsed>;
viewer.appendPreview(log);
});
The same works also for the preview.php. In such case you need to handle onPreviewInit event.
$("#content").bind("onPreviewInit", function(event)
{
var viewer = event.target.repObject;
viewer.loadHar(<path-to-har-file>);
});
Available since HAR Viewer 2.0.15
List of visible columns used in HAR timeline waterfall graph can be customized through a cookie: previewCols or through API.
$("#content").bind("onViewerInit", function(event)
{
var viewer = event.target.repObject;
// Display URL, Status, Size and Timeline columns by default
// Do not touch cookies (the second parameter is true)
viewer.setPreviewColumns("url status size timeline", true);
});
The first argument specifies list of column IDs separated by a space (see available columns). The second argument says whether touching cookies should be avoided.
Do you need more? Please create a report.