[SalesForce] Error: Element type “div” must be followed by either attribute specifications, “>” or “/>”

Error: Element type "div" must be followed by either attribute
specifications, ">" or "/>".

<apex:page standardController="ADSS_Platform_Account__c" showHeader="false" standardStylesheets="false">   
    <div style="font-family: sans-serif; font-size: 12px;color: #ffffff;" "height: 100%" class="bodyDiv"  onclick="resizeFrame();">  
        <c:IBHierarchyTree currentId="{!ADSS_Platform_Account__c.id}"/>   
    </div>  
</apex:page>

I removed left angular brackets because i was not able to post my code.

Best Answer

height: 100% falls under style-size attribute string , thus

" font-family: sans-serif; font-size: 12px;color: #ffffff; " and " height: 100% " should be written as same string as ,

style=" font-family: sans-serif; font-size: 12px;color: #ffffff;height: 100% "

Please hit like , if you find the information relevant.

Related Solutions

[SalesForce] apex:inputText disabled binding causing “element value must resolve to a String type!”

Can you just use outputText instead if it needs to be disabled? Not the same appearance but might work for you?

<apex:outputText id="impressions" value="{!drop.impressionsRequested}" rendered="{!dropObj.impressionsDisabled}"/>

<apex:inputText id="impressions" value="{!drop.impressionsRequested}" rendered="{!NOT(dropObj.impressionsDisabled)}"/>

Or instead out output text you could just use a disabled HTML input element so it would maintain the same look:

<apex:outputPanel layout="none" rendered="{!dropObj.impressionsDisabled}">
    <input type="text" value="{!drop.impressionsRequested}"/>
</apex:outputPanel>

[SalesForce] Reason behind element value must resolve to a String type!

This looks to be a bug in Visualforce - its been around since 2008 by the look of this post on the Developerforce Discussion Boards:

https://developer.salesforce.com/forums/ForumsMain?id=906F0000000951yIAA

The best I've been able to do with this is to have the underlying property still stored as an Integer, but have a string based getter/setter for it that converts to/from a string. That way I can use the property as an Integer within my code and I just have to convert it once.

You'll need an answer from Salesforce as to why it works this way - given that people have been complaining about this behaviour for nearly 6 years, it feels like they might think its working correctly. Although Doug Chasman does suggest its a bug in the developerforce post above.

Best Answer

Related Solutions

[SalesForce] apex:inputText disabled binding causing “element value must resolve to a String type!”

[SalesForce] Reason behind element value must resolve to a String type!

Related Topic