Arabic and right-to-left

What the components handle, what they do not, and THE NUMERAL SYSTEM TRAP — a quantity in the wrong digits BESIDE ONE IN THE RIGHT ONES. Half of this estate's users read Arabic, so this is not an internationalisation afterthought — it is half the application, and it fails in ways an English-reading developer cannot see. WHAT THE COMPONENTS HANDLE IS THE LAYOUT MIRRORING. Set the direction and the page reverses: alignment, order, controls, scrollbars. That part works, and it is the part people worry about. WHAT THEY DO NOT HANDLE IS ANYTHING YOU BUILT WITH A DIRECTION ASSUMED. A margin on the left, an icon meaning "next" that points one way, a fixed pixel position. Use logical properties — start and end — so the page mirrors rather than needing a second version of itself. AND THE NUMERAL TRAP IS THE ONE THIS PLATFORM HAS RECORDED HITTING REPEATEDLY, SO…

In this module: Module 7 · Binding data to the page

1. 1Binding, and what the framework does for you
2. 2Tables and lists
3. 3Forms and two-way binding
4. 4Formatting: dates, numbers and currency
5. 5Arabic and right-to-leftFree preview
6. 6Conditional display
7. 7Sorting, filtering and searching
8. 8Empty, loading and error states
9. 9What breaks: three binding failures
10. 10Lab briefing · One screen, every state