[CB-4644] File API documentation - FileReader headings are incorrect

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.9.0
• Assignee: Lorin Beer
• Reporter: Peter
• Created: 22/Aug/13 06:16
• Updated: 23/Aug/18 06:44
• Resolved: 03/Sep/13 17:57

Description

Many the headings in the FileReader section are incorrect and/or inconsistent with other sections making it difficult to read

For example,

• "Read As Data URL" - this is a function name. Heading should be "readAsDataURL"
• Quick Example for readAsDataURL - should be h3 not h2

• "Abort Quick Example" - should be h2 "abort" (because it is a function name)
• This abort section seems misplaced - it is currently between the Quick and Full example for readAsText?
• "Quick Example" should be h3.

• "Read As Text" - this is a function name. Heading should be "readAsText"
• Quick Example for readAsText - should be h3 not h2
• Full Example for readAsText - should be h3 instead of h2
• iOS Quirks for readAsText - should be h3 not h2

• "Read As Binary String" - this is a function name. Heading should be "readAsBinaryString"
• Quick Example for readAsBinaryString - should be h3 not h2

• "Read As Array Buffer" - this is a function name. Heading should be "readAsArrayBuffer"
• Quick Example for readAsArrayBuffer - should be h3 not h2