Visualforce Developer Guide

Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
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
Visualforce Charting Limitations and Considerations
How Visualforce Charting Works
Building a Complex Chart with
Updating Charts with Refreshed Data
Controlling the Appearance of Charts
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

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Visualforce Charting Limitations and Considerations

This section lists considerations and known limitations for Visualforce Charting.

  • Visualforce charts only render in browsers which support scalable vector graphics (SVG). For more information, see W3C SVG Working Group.
  • Visualforce charting uses JavaScript to draw the charts. Visualforce charts won’t display in pages rendered as PDFs.
  • Email clients don’t usually support JavaScript execution in messages. Don’t use Visualforce charting in email messages or email templates.
  • Visualforce charting sends errors and messages to the JavaScript console. Keep a JavaScript debugging tool, such as Chrome DevTools or Safari Web Inspector, active during development.
  • Dynamic (Apex-generated) charting components aren’t supported at this time.