Last Updated on March 2, 2016

Caspio 9.1 is scheduled to be released in March 2016. The following is a list of product areas and functions that will be impacted in this release.

Deprecated “Name” Attribute in <TABLE> and <TR> Tags

Change area Rendered DataPages
Impact area Any custom JavaScript or CSS that relies on the “name” attribute in <TABLE> and <TR> tags (i.e. name = “cbTable” or name = “groupX”)
Description As announced in November 2015, the “name” attribute for <TABLE> and <TR> tags will be deprecated to ensure full HTML5 compatibility of our applications. In the 9.1 release, “name” will be replaced with the “data-cb-name” attribute. Going forward, “data-cb-name” will remain intact as it currently exists now.

If you have inserted custom JavaScript or CSS that refers to the “name” attribute, or if you implemented Responsive DataPages, you will need to make the change now. The Responsive DataPages instructions have been updated with revised code.

 

Deprecated “Width” Attribute in <TD> and <TH> Tags

Change area Rendered DataPages
Impact area Any JavaScript or CSS that relies on the “width” attribute in <TD> and <TH> tags
Description As announced in November 2015, the “width” attribute in <TD> and <TH> will be deprecated due to compatibility with HTML5.

If you have inserted custom JavaScript or CSS that refer to the “width” attribute, you will need to make the change now.

 

“Name” Attribute in <A> and <DIV> Tags to be Deprecated in May 2016

Change area Rendered DataPages
Impact area Any custom JavaScript or CSS that relies on the “name” attribute in <A> and <DIV> tags
Description The “name” attribute in <A> and <DIV> will be removed in May 2016 due to compatibility with HTML5. We have introduced a new “data-cb-name” attribute in <A> and <DIV> tags used in JumpTo, BulkDeleteButton, BulkEditButton, GridEditButton, SearchAgainButton, DataDownloadButton, cbFormCalendar, and error message elements.

If you have inserted custom JavaScript or CSS that refers to the “name” attribute in these areas, you will need to prepare for this deprecation over the next two months.

 

“Name” Attribute in Navigation Tables to be Deprecated in May 2016

Change area Rendered DataPages
Impact area Any custom JavaScript or CSS that relies on the “name” attribute in <TABLE> tags for top and bottom navigation tables (i.e. name=”cbNavigationTableBottom” and name=”cbFormNavigationTableTop”).
Description The “name” attribute in <TABLE> tags for top and bottom navigation tables will be removed in May 2016 due to compatibility with HTML5.

We have introduced a new “data-cb-name” attribute in <TABLE> tags used for cbFormNavigationTableTop and cbNavigationTableBottom elements.

If you have inserted custom JavaScript or CSS that refers to the “name” attribute in these areas, you will need to prepare for this deprecation over the next two months.

 

Change to Data Transfer Calculation

Change area Data transfer related to data backup during import
Impact area On-demand or scheduled import tasks with backup option enabled
Description Data transfer resulting from backing up objects during on-demand or scheduled import tasks (DataHub) will accrue data transfer.

 

End of Support for WML DataPages

Change area Rendered DataPages
Impact area WML DataPages
Description WML DataPages will no longer be supported after the 9.1 release and will be removed from all customer accounts. WML DataPages were designed to provide limited app functionality on traditional (non-smart) phones.

Customers are encouraged to replace any active WML DataPages with standard Submission Form DataPages prior to the 9.1 release.

 

Scripts Contained Inside Table Fields Will No Longer Execute

Change area Rendered DataPages
Impact area Any custom script contained inside table fields or passed parameters
Description A common way to enhance DataPages is to insert scripts (such as JavaScript, vbscript, livescript, mocha, -moz-binding) into HTML blocks, headers, footers and labels. This functionality will continue to operate normally.

However, beginning in the 9.1 release and as a safeguard for your users, scripts contained inside table fields or passed parameters will no longer execute in HTML blocks, headers, footers, and labels, and any links within them will be displayed in plain text.

This should not affect most applications because scripts are typically inserted directly in DataPages rather than database fields or passed parameters. Parameters can still be used normally in scripts which are inserted directly in DataPage headers, footers, HTML blocks, etc.

 

Fixed the Response of DeleteData Method

Change area WS API
Impact area DeleteData Method
Description Response from DeleteData method now returns the correct number of deleted records instead of 0. If you had written code to bypass this bug, you will need to review your code after the release.

 

Changes to Caspio Branding Container

Change area Branded DataPages Accessed via Direct URL
Impact area Any custom JavaScript or CSS that relies on the number of HTML tables and rows
Description In this release, the outer table containing Caspio branding is removed and a simplified branding snippet is added in its place.

If you have inserted custom JavaScript or CSS that relies on the number of tables and rows, you will need to adjust your code after the release.

 

Standardized Input and Output Date Format for Date/Time Field

Change area Rendered DataPages
Impact area Any custom JavaScript that relies on the old M/d/yyyy format in Text Fields, Hidden Fields, Dropdowns, Listboxes, Radio Buttons, Cascading Fields, Display Only Values, and Parameters
Description MM/dd/yyyy is the new default format for date/time fields. Essentially, the Month values will contain a leading zero when necessary.

If your custom JavaScript code relies on the old format, you will need to adjust your code after the release.