wordpress-mobile / wordpress-mobile/WordPress-Android
Pages List: HTML characters are not rendered correctly in page title
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Expected behavior
Page titles are rendered with decoded HTML entities on pages list, just like they are rendered in the posts list.
The ampersand (&) character is a special case because it can be quickly added using the device keyboard by just tapping on the & key. In order to add other HTML entities the user has to switch the editor to HTML mode and type the encoded HTML entity code manually.
Actual behavior
HTML entities are rendered encoded in the pages list:
| Pages List | Posts List |
|---|---|
![]() |
![]() |
Steps to reproduce the behavior
- From My Site → Pages
- Tap on the blue floating action button in the bottom right of the screen to add a page
- Type
Testing & in page titleusing the device keyboard - Tap PUBLISH button at the top right of the editor screen
- Notice on the pages list that the title of the newly created page shows up as
Testing & in page title.
Optional:
Create another page, switch to the HTML editor and enter manually an encoded html entity like: ;copy; and notice it also doesn't get rendered correctly.
Preview
![]() |
Ideally all HTML entities are rendered decoded in the list of pages, which is already working as expected for posts.
Tested on Samsung Galaxy S8+, Android 9, WPAndroid 19.1
Tested on Emulator, Android 11, WPAndroid alpha-342 (1)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing how page titles and post titles are rendered in the Android app, reproducing the issue from My Site → Pages with an ampersand and another HTML entity. The work is done when entities display decoded in the pages list, matching the posts list behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100


