Permalink
Browse files

Allow docs to run inside iframe.

  • Loading branch information...
nene committed Apr 26, 2012
1 parent baeb7b1 commit 52a65bc217a0af7e4d61e54e9f9f7c9d1d1dc230
Showing with 3 additions and 0 deletions.
  1. +3 −0 template/app/History.js
View
@@ -8,6 +8,9 @@ Ext.define("Docs.History", {
* Initializes history management.
*/
init: function() {
+ // allow Docs to work inside iframe
+ Ext.util.History.useTopWindow = false;
+
Ext.util.History.init(function() {
this.historyLoaded = true;
this.initialNavigate();

3 comments on commit 52a65bc

@SteveSchreiner

This comment has been minimized.

Show comment Hide comment
@SteveSchreiner

SteveSchreiner Apr 26, 2012

First, thanks for the quick attention to the issue I found! We downloaded jsduck 3.9.1 and re-generated our docs (we currently use extjs-4.1-rc1) and the problem still exists. Is there something else we need to do?

First, thanks for the quick attention to the issue I found! We downloaded jsduck 3.9.1 and re-generated our docs (we currently use extjs-4.1-rc1) and the problem still exists. Is there something else we need to do?

@nene

This comment has been minimized.

Show comment Hide comment
@nene

nene Apr 26, 2012

Member

Well, the fix is not part of 3.9.1. It'll be fixed in next release, which will probably be next week.

If you need it faster, you can just inject this one line inside the jsduck-generated page.

Member

nene replied Apr 26, 2012

Well, the fix is not part of 3.9.1. It'll be fixed in next release, which will probably be next week.

If you need it faster, you can just inject this one line inside the jsduck-generated page.

@shmeltex

This comment has been minimized.

Show comment Hide comment
@shmeltex

shmeltex Apr 26, 2012

Thank you for this change!

Thank you for this change!

Please sign in to comment.