This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
getting error: Unexpected symbols found ";" Unexpected symbols found " " wit code: <div style="width:{T{$l.width}T}">bar</div>
custom delimiters was defined globally
custom delimiters were defined globally
fixed in http://hg.netbeans.org/main/contrib/rev/69f4f57f3a36 should be working well in version 1.21 - it could be tomorrow on Dev UC
So ver. 1.21 is on Dev UC now, so feel free to try if all your troubles with editor Hints were fixed or not.
If you add 'px' after closing delimiter, error is still there <div style="width:{T{$l.width}T}px">bar</div>
From behavior it seems that metaData which are holding delimiters aren't acting in unified way for delimiters entered in project properties and in the options. I found out that the metaData support is written really badly, so I will fix it soon.
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/0469afeee1ea User: Martin Fousek <marfous@netbeans.org> Log: #184263: syntax errors, #184264: unexpected symbols errors
OK, so: <div style="width:{T{$l.width}T}">bar</div> - works well <div style="width:{T{$l.width}T}px">bar</div> - works well <div style="width:{T{$l.width}T}px;">bar</div> - syntax error Just the last case has to be still fixed. BTW, it works well with default {,} delimiters and now we are also supporting Smarty3 syntax. So I would probably recommend to stop using custom delimiters and upgrade to the newest smarty version where are troubles with mixed JS/Smarty resolved in more elegant way.
I can not repeat this error - as it looks good to me. Product Version: NetBeans IDE 7.2 RC1 (Build 201206141830) Java: 1.7.0_05; Java HotSpot(TM) Client VM 23.1-b03 System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb)
(In reply to comment #9) > I can not repeat this error - as it looks good to me. Me neither. Thanks efremmc2 for trying that out - probably there was changed something in css editor. Rest of the issue was resolved by the web-main #0469afeee1ea so marking as fixed.