browser navigation

  • Backwards & Forwards history navigation has several issues.
    • note: The web standards community is working on improving the browser-history API, since many other “Single Page Applications” (SPA) are running into the same issues.
    • See also: App History API (proposal)
  • Reloading complex-encoded URLs does not always work, due the mis-encoding of the URL parameters. This is a tricky issue, for which the causes which will need to be carefully studied, tested and fixed. Research what tools could be used to help debug this issue.
    • There is a need to have a better workflow & tooling to help with debugging these URL-issues.
  • URL hash handling
    • Fix the hash-handling conflict between the inline-category widget and Wikipedia ToC clicks.
    • Always reset the hash when needed (eg. when clicking on another topic) (partly fixed)
    • Scroll-position / section alignment issue for Wikipedia (example)

mobile browser compatibility and usability

  • Fix bugs in mobile panel loading/clearing
  • Cold-startup time (upon first use) is quite slow - sometimes more than 10-20 seconds on low-bandwidth networks
  • The Apple iOS mobile browser needs more UX testing & fixing.
  • The Wikipedia-app needs a “Table of Content” system suited for mobile devices. Currently it has no ToC.

quality assurance

  • Accessibility (including keyboard-access) should be assessed and improved where needed.
    • Integrate an automated accessibility test system.
    • Look into the IBM Carbon web-component framework for accessible replacements (when needed)
  • Integrate an automated testing system.
  • Get more UX feedback from real users.

admin-dev workflows

field localization

  • Create a structure to store field-label translations (title and icon-title), both for Wikidata and non-Wikidata fields.
    • Allow the json2fields script to fetch and store property translations too.
  • Cleanup design any remaining inconsistencies of the field definitions.

Wikidata/Wikipedia issues encountered

  • Difficulty avoiding duplicate items in more complex/stacked SPARQL queries (there are some ways, but it is not easy to generalize to all SPARQL queries). (experiment more with “GROUP BY”)
  • Wikidata: claim-statements integration not done yet, because the data-access is more complex when using wikibase-sdk (with claims).
  • Integrating Wikidata localization data for properties.
  • Abandoned Wikidata-based applications.
  • Wikipedia: Image-loading blocking sometimes (“too many image requests”)


  • How to detect if the field URL could be embedded (instead of opening a a new tab)? (run a headless browser loading an iframe with the URL, checking for CORS-errors?)
  • JSON-LD enhancement: “Add schema:about properties that include #Wikidata (/entity/{id}) and #DBpedia (/resource/{id}) identifiers as property values.” * (this is useful when there are multiple subjects, beyond the main subject)