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
Overriding Buttons, Links, and Tabs with Visualforce
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrating Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
Salesforce Platform Development Process
Tell Me More: Where Visualforce Pages Can Appear in the Salesforce App
Guidelines and Best Practices
Sharing Visualforce Pages Between Mobile and Desktop
Excluding Visualforce Pages from Mobile or Desktop
Creating Visualforce Pages That Work in Mobile and Desktop
Choosing an Architecture for Visualforce Pages in the Salesforce App
Optimizing the Performance of Visualforce Pages in the Salesforce App
Visualforce Components and Features to Avoid in the Salesforce App
Known Visualforce Mobile Issues
Access or Permission Issues
Device Sensor Issues
Input Issues
Loading and Performance Issues
Navigation Issues
Network Issues
Salesforce Classic vs. Lightning Experience Issues
Updating Records Issues
User Interface Issues
Considerations and Limitations for Using Visualforce in the Salesforce App
Prepare a Support Request for Problems with Visualforce Pages in the Salesforce App
Choosing an Effective Page Layout
User Input and Interaction
Managing Navigation
Introduction to the Salesforce Lightning Design System
Using Visualforce Pages as Custom Actions
Performance Tuning for Visualforce Pages
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Best Practices
Standard Component Reference
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Salesforce Classic vs. Lightning Experience Issues

These issues are caused by switching between Salesforce Classic and Lightning Experience.
Issue Solution
A UI check incorrectly returns Theme4t instead of Theme3 when the user is using the Classic UI on mobile devices. This issue occurs with Visualforce global $User.UIThemeDisplayed and Apex class UserInfo.getUiThemeDisplayed commands. Check the user’s current UI by verifying if the sforce.one JavaScript object is available; this object is not available in the Classic UI.