I have a Simple XML form with three input elements. The relevant code reads:
<form> <fieldset autoRun="false"> <input type="time" searchWhenChanged="true"> <label>Time range:</label> <default> <earliestTime>-1h</earliestTime> <latestTime>now</latestTime> </default> </input> <input type="text" token="FilterString"> <label>Filter:</label> </input> <input type="text" token="HostFilter"> <label>Machine:</label> </input> </fieldset>
When I access the form's through its regular URL:
the URL is immediately replaced with:
Obviously the form's tokens are mapped into HTTP GET parameters stored in the URL. However, that more or less breaks the browser's back (to last page) functionality. Clicking
back once changes the URL to:
back a second time changes the URL to the original value without HTTP GET parameters:
Only when I click
back a third time I get the URL of the page I had visited before the current dashboard.
This is pretty bad from a user experience point of view. Is this a bug?
More information: I have observed this with Splunk 6.1.3. It seems to be caused by the parameter
searchWhenChanged="true" of the
input type="time". But I need that: when I set
false that dashboard's searches do not run until I manually click
Submit. My current Advanced XML dashboards to not exhibit this problem.
Posting a comment because for some reason I cannot edit my question. The problem affects the app "Splunk 6.x Dashboard Examples", too. It is nearly impossible to go back from the dashboard "simplexmlexamples/simpleformadvanced".
The intention of the back button in the current UI is to go to the previous state. For example when running a series of searches, clicking back goes to the prior search. This means that:
It's quite possible that there are warts in the functionality which should be duly logged, triaged, and so on, but simple capacity for the back button to not leave the view is by design. It's pretty essential for some views to behave pleasantly.
However what I think you're saying is that simply navigating to a page without interacting with it leads to a series of url updates which cause the back button to not perform as a user would expect. If true, I don't know if it's a design flaw, a silly design, or a bug, but it's worth raising with technical support, IMO.