-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
flutter/packages
#6879Closed
Copy link
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.c: tech-debtTechnical debt, code quality, testing, etc.Technical debt, code quality, testing, etc.fyi-ecosystemFor the attention of Ecosystem teamFor the attention of Ecosystem teampackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.platform-webWeb applications specificallyWeb applications specificallyteam-webOwned by Web platform teamOwned by Web platform teamtriaged-webTriaged by Web platform teamTriaged by Web platform team
Description
Right now, all the web unit tests in flutter/packages run against the HTML renderer. If we are going to run them against only one renderer, CanvasKit should probably be the one we test. Or we could test both. But right now, HTML is our least recommended renderer option, and so our tests should probably not default to that.
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.c: tech-debtTechnical debt, code quality, testing, etc.Technical debt, code quality, testing, etc.fyi-ecosystemFor the attention of Ecosystem teamFor the attention of Ecosystem teampackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.platform-webWeb applications specificallyWeb applications specificallyteam-webOwned by Web platform teamOwned by Web platform teamtriaged-webTriaged by Web platform teamTriaged by Web platform team