Page MenuHomePhabricator

[EPIC] Use MCS as parser for main content in mobile web
Closed, DeclinedPublic

Description

This will enable us to support sentence editing/content transformations and I suspect things such as re-positioning components such as infoboxes on small screens.

Initial thought is we'd aim to do this in the "beta" channel of mobile first, and then roll out from there.
We are aware that Parsoid has no support for video and audio tags right now, but given support in mobile is currently low (and broken) given the expected performance benefits this is an acceptable trade off.

Concerns that need to be addressed:

  • How is audio and video impacted? https://phabricator.wikimedia.org/T64270 and how does this differ from existing experience
  • How does this impact editing? (I would suspect no impact on short term, possible impact on long term)

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

Jdlrobson raised the priority of this task from to Needs Triage.
Jdlrobson updated the task description. (Show Details)
Jdlrobson added a project: Web-Team-Backlog.
Jdlrobson moved this task to 2015-16 Q2 on the Web-Team-Backlog board.
Jdlrobson subscribed.
Jdlrobson renamed this task from [Epic] Use Parsoid as backend for mobile web to [Epic] Use Parsoid as parser for main content in mobile web.Jun 1 2015, 11:02 PM
Jdlrobson set Security to None.
phuedx renamed this task from [Epic] Use Parsoid as parser for main content in mobile web to [EPIC] Use Parsoid as parser for main content in mobile web.Jun 2 2015, 1:41 PM
phuedx added a project: Epic.
Jdlrobson raised the priority of this task from Low to High.Dec 22 2015, 10:29 PM
Jdlrobson renamed this task from [EPIC] Use Parsoid as parser for main content in mobile web to [EPIC] Use MCS as parser for main content in mobile web.Mar 9 2017, 7:07 PM
Jdlrobson moved this task from 2015-16 Q2 to Epics/Goals on the Web-Team-Backlog board.