Visualforce Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
Styling Visualforce Pages
HTML Comments and IE Conditional Comments
HTML Tags Added or Modified by Visualforce
Relaxed Tidying for the HTML5 Doctype
Manually Override Automatic <html> and <body> Tag Generation
Creating an Empty HTML5 “Container” Page
Using a Custom Doctype
Change the MIME type of Your Visualforce Page
Setting Custom HTML Attributes on Visualforce Components
Render a Visualforce Page as a PDF File
Standard Controllers
Standard List Controllers
Custom Controllers and Controller Extensions
Advanced Examples
Override Buttons, Links, and Tabs with Visualforce
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrate Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Communicating Across the DOM with Lightning Message Service
Visualforce Best Practices
Standard Visualforce Component Reference
Appendices
PDF

Manually Override Automatic <html> and <body> Tag Generation

Use the applyHtmlTag and applyBodyTag attributes of the <apex:page> tag to suppress the automatic generation of <html> and <body> tags, in favor of static markup you add to the page yourself.
Here’s an example that illustrates how to do this:
<apex:page showHeader="false" sidebar="false" standardStylesheets="false"
    applyHtmlTag="false" applyBodyTag="false" docType="html-5.0">

<html>
    <body>
        <header>
            <h1>Congratulations!</h1>
        </header>
        <article>
            <p>This page looks almost like HTML5!</p>
        </article>
    </body>
</html>

</apex:page>

The attributes act independently of each other; you can use them in any combination of true, false, or unset. When both attributes are set to true, the default, automatic generation of <html> and <body> tags is preserved. When either is set to false, you are fully responsible for adding the corresponding tags to your markup. In this mode, Visualforce won’t prevent you from creating nonsense tag combinations or attributes that give even modern browsers fits.

A <head> section is always generated if required, regardless of the values for applyHtmlTag and applyBodyTag. For example, a <head> tag is generated if you use <apex:includeScript> or <apex:stylesheet> tags, set the page title, and so on.

There’s one exception to this rule. If applyHtmlTag is set to false and there are no other elements in the page except for <apex:includeScript>, no <head> is generated. For example, the following code automatically adds <body> tags, but doesn’t add a <head> section: This behavior shouldn’t cause problems for real-world pages.
<apex:page showHeader="false" applyHtmlTag="false">
<html>
    <apex:includeScript value="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"/>
</html>
</apex:page>

Note

The applyHtmlTag attribute is available on the <apex:page> tag for Visualforce pages set to API version 27.0 or higher. The applyBodyTag attribute is available on the <apex:page> tag for Visualforce pages set to API version 28.0 or higher. They both have the following additional restrictions:
  • The showHeader attribute must be set to false for the page, for example, <apex:page showHeader="false">.
  • The contentType attribute must be set to “text/html” (the default).
  • The values for the top level, or outermost, <apex:page> tag are used; applyHtmlTag and applyBodyTag attributes on pages added using the <apex:include> tag are ignored.