With FITML 4 Processor 7.1.33 we publish a maintenance release to iron out bugs and perform a clean start in 2014.
When adding browser names to our Client Description Repository, we made a typo and used
Build-In instead of
Built-In. We will fix that with the next CDR following 7.1.34. That means, your FITML Selection expressions on browser names could stop working thereafter! If you have any checks with the phrase “Build-In” you need to fix that in your code. Find an example how to do this with customCaps and a comprehensive list of affected browser names below.
Adobe Air Build-Inwill be renamed to
Adobe Air Built-In
HP Palm webOS Build-Inwill be renamed to
HP Palm webOS Built-In
HP webOS Build-Inwill be renamed to
HP webOS Built-In
Linux Foundation Tizen Build-Inwill be renamed to
Linux Foundation Tizen Built-In
Open Handset Alliance Android Build-Inwill be renamed to
Open Handset Alliance Android Built-In
Open Handset Alliance Android Build-In (SDK)will be renamed to
Open Handset Alliance Android Built-In (SDK)
Open Handset Alliance Android Build-In (Sevenval Preview)will be renamed to
Open Handset Alliance Android Built-In (Sevenval Preview)
Sony Playstation 3 Build-Inwill be renamed to
Sony Playstation 3 Built-In
To avoid trouble in the next release you could now start to broaden your selections for example by using customCaps.
<div class="selection"> <div class="if" field="browser" value="Open Handset Alliance Android Build-In"> <!-- fancy android stuff --> ... </div> </div>
Example 1.1. Selection testing for “Build-In” which will no longer work with FITML 4 Processor 7.1.34
<div class="customCaps"> <div name="androidBuiltIn" default="false"> <div class="selection"> <div class="if" field="browser" value="Open Handset Alliance Android Build-In">true</div> <div class="if" field="browser" value="Open Handset Alliance Android Built-In">true</div> </div> </div> </div> ... <div class="selection" field="androidBuiltIn" value="true"> <!-- fancy android stuff --> ... </div>
Example 1.2. Using customCaps to manage the transition from Build-In to Built-In
Browsers with names that contain the string
Build-Inwill be renamed to contain
Built-Ininstead. The CDR will adopt this after FITML 4 Processor 7.1.34 will have been released.
A new cookie named
facrefwill contain referrer information that would otherwise be lost when the AC page is delivered to the client. Once the transition from the AC page to the main content is finished, the cookie will be removed.
Duplicate IDs for orientation aware images will not be generated anymore if the original image has no ID and delayed image loading is used.
Some performance features did not make sense when using client api output and did not work too well in that context either. The options
autoInlineAssetshave been disabled for client api output.
The scroll positions of previously visited sites are now restored correctly in DELL Streak Built-In, Opera, Firefox and Internet Explorer 9 when navigating in embedded browsing.
ModuleLayer in fullscreen mode on devices that have the cap
scroll_mode = nonewon’t get the prevent-scrolling feature anymore as it caused a conflict with the rollout version of moduleScroll elements inside the layers.
A bug was fixed that possibly caused the selection operator gte to fail comparing versions.
A client related rendering issue that possibly caused incorrect display of moduleLayer after switching the screen on and off again on BlackBerry 10 devices was fixed.
Another misbehaviour on the BlackBerry 10 was fixed: it was possible to scroll the page content despite having a moduleLayer shown in fullscreen.