Closed
Bug 1079694
Opened 11 years ago
Closed 10 years ago
Remove all use of fx-embedded-call-button-spacer in Loop UI content markup
Categories
(Hello (Loop) :: Client, defect)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
WONTFIX
| backlog | tech-debt |
People
(Reporter: NiKo, Unassigned)
Details
(Whiteboard: [tech-debt])
We shouldn't use markup to space elements, eg.:
<div>
<div className="fx-embedded-call-button-spacer"></div>
<AcceptCallButton mode={this._answerModeProps()} />
<div className="fx-embedded-call-button-spacer"></div>
</div>
Instead, we should define reusable style rules applicable for targeted elements.
|
||
Updated•11 years ago
|
Whiteboard: [tech-debt]
|
||
Updated•11 years ago
|
backlog: --- → Fx36+
|
|
||
Updated•11 years ago
|
backlog: Fx36+ → Fx37+
|
|
||
Updated•10 years ago
|
backlog: Fx37+ → Fx38?
|
|
||
Comment 1•10 years ago
|
||
Moving these to blocking-loop="tech-debt" so they can be triaged against other tech debt bugs. When we take a tech-debt bug to work on - just mark it "firefox-backlog"+ and give priority. Then we'll pull it during iteration planning (or factor it into workload if someone is already working on).
backlog: Fx38? → tech-debt
|
|
||
Comment 2•10 years ago
|
||
We are currently reworking the Loop "user journey" (bug 1209713) and as part of this direct calls and contacts are being removed. Therefore closing direct call related bugs as wontfix.
Tracking id: directcallclosing
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•