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.

Technically, there was both a bug (as you mentioned regarding the id) and some doc issues. There are currently a bunch of inherited Panel members that still need to be @hidden, which is indeed a doc issue. Those should be removed in the next release.

Fine. However, my issue is that there seem to be numerous discrepencies between the docs and the actual components. For example, if I create a fieldset (or panel) and use Ext.get() to attach to it, there is no disable() method listed for the component, dispite it being present in the docs.

Fine. However, my issue is that there seem to be numerous discrepencies between the docs and the actual components. For example, if I create a fieldset (or panel) and use Ext.get() to attach to it, there is no disable() method listed for the component, dispite it being present in the docs.

Ext.get() returns an Ext.Element. You want Ext.getCmp() to return a Component. They are two different APIs for two different types of objects.

There is something wrong with the formatting for the update method (this is different from what has already been mentioned). Look at the params option in the options object:

Code:

If tt>true any <>script> tags embedded in the response text will be extracted and executed. ....

I think it might be just an issue with the "<" brackets in the source.

Second, I think there are some options for the update method that appear to be missing. Just reviewing the example below the options, you can see discardUrl, nocache, text and scripts is missing. The indentation of the options that are present is not quite right too.

Third, there is a minor typo in the update example:

Code:

scripts: false // Save time by avoiding RexExp execution.

Fourth, take a look at the code in the Usage section at the very top of the Ext.Updater page. It has a line of code that looks like this:

Code:

mgr.update("http://myserver.com/index.php", "param1=1&param2=2");

It doesn't look like that parameter pattern is supported by the update docs. Either the example is wrong or the update method docs are missing something.