First, I find it a little odd that WebHistory.go throws an exception if the resulting position is out of bounds, whereas WebHistory.goBack and WebHistory.goForward, in conceptually the same situation, do not throw any exceptions and silently act as no-ops.
I think I also find little value in WebHistory.goBack and WebHistory.goForward without WebHistory.canGoBack and WebHistory.canGoForward, as I can achieve the same results with go(-1) and go(+1), which is more compact and by definition consistent with other uses of WebHistory.go.
I also think that the WebHistory.maxSize property should throw an exception when the user attempts to set it to an illegal value, for consistency with WebHistory.go and the rest of JavaFX.
- blocks
-
JDK-8117444 WebHistory.setMaxSize: property and setter method work differently
- Closed
-
JDK-8126018 WebHistory.goFoward() causes an exception when called in newly created WebEngine
- Closed
- relates to
-
JDK-8126356 WebHistory: java.lang.ArrayIndexOutOfBoundsException exception is thrown when setting a history maximum size to a newly created WebEngine
- Resolved
-
JDK-8117444 WebHistory.setMaxSize: property and setter method work differently
- Closed
-
JDK-8126018 WebHistory.goFoward() causes an exception when called in newly created WebEngine
- Closed
-
JDK-8101236 Provide a Browser History API
- Closed