Documentation Bugs - Ext 2.x

Quote:

---

Originally Posted by mjlecomte

...Ext.Ajax

Several properties not itemized in the docs per the example.

Code:

---

// Basic request
Ext.Ajax.request({
  url: 'foo.php',
  success: someFn,
  failure: otherFn,
  headers: {
      'my-header': 'foo'
  },
  params: { foo: 'bar' }
});
...

---

---

The success, failure, headers, and params options to the request method are all documented in the API docs are far as I can tell: http://extjs.com/deploy/dev/docs/?cl...member=request Am I missing the point of your post?

Woops! My mistake, should have went to bed....:">
I retract my comment.

Quote:

---

Originally Posted by tjcrowder

The success, failure, headers, and params options to the request method are all documented in the API docs are far as I can tell: http://extjs.com/deploy/dev/docs/?cl...member=request Am I missing the point of your post?

---

There was just a mistake in closing a <b> tag which I use to highlight property names, so it's difficult to visually seperate the options. I fixed most of these mistakes in SVN as soon as the latest RC1 docs were released.

It's not easy to get docs right when the only time you see the results of your work is the few occasions that the docs are regerenerated.

TabPanel's tab's config options (tabTip, closable, etc) are not documented

There is no documentation for Panel.draggable.

Panel.draggable can contain also drag config object; it is {Boolean/Object} type.

GridPanel.ddGroup is not documented.

Something that could be clarified or added to the docs is that iconCls is user specified (not in ext-all.css). It's something that eluded me as a noobie.

Thread

Quote:

---

Originally Posted by tryanDLS

EditorGrid is overriding trackMouseOver to false, but it's marked as private, instead of a config entry, so it's not getting doc'd correctly.

---

As far as I can tell docs show it as a config entry, but show it defaults to true, which is not the case.

I keep running into issues with the fieldset vs panel components. I don't know whether it's a bug with extending the component, or an issue with documenting things, or what. For example, if you create a form with a panel item, you can set the id property in the config. But if you switch to a fieldset, the id will not be set. Also, when I create the objects, neither one seems to have the disable() method.

end-user -

Please place this type of post in the help section for future reference as this is not a documentation issue. There was a bug in the fieldset code which did not take the id into account when generating the html. This has been resolved in SVN and you can find a workaround here until the next release.