".js component without matching .manifest" error message should point to MDC

RESOLVED FIXED in mozilla2.0b7

Status

()

Core
Build Config
RESOLVED FIXED
8 years ago
7 years ago

People

(Reporter: philikon, Assigned: philikon)

Tracking

unspecified
mozilla2.0b7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

Comment hidden (empty)
Created attachment 464065 [details] [diff] [review]
v1
Assignee: nobody → philipp
Attachment #464065 - Flags: review?(ted.mielczarek)
Attachment #464065 - Flags: review?(ted.mielczarek) → review+
(Assignee)

Updated

8 years ago
Keywords: checkin-needed

Updated

7 years ago
Attachment #464065 - Flags: approval2.0?
Created attachment 476702 [details] [diff] [review]
v1 (exported) for checkin

This is the patch in v1, just with hg headers from an export, to make it easier to push. (I was getting ready to push it after today's downtime as a "hope we're safe" run when someone beat me, so this is going in as a ridealong)
Attachment #464065 - Attachment is obsolete: true
Attachment #476702 - Flags: review+
Attachment #464065 - Flags: approval2.0?
Pushed:
http://hg.mozilla.org/mozilla-central/rev/c6e08993db4c

I'm really sorry Philipp, I forgot to change the username of the commit :(
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b7
No big deal, thanks for landing!

Updated

7 years ago
Blocks: 603866
You need to log in before you can comment on or make changes to this bug.