WebDriver/RemoteProtocol/Meetings/2019/03/04: Difference between revisions

WebDriver/RemoteProtocol/Meetings/2019/03/04 (view source)

Revision as of 11:38, 4 March 2019

48 bytes removed , 4 March 2019

fix mistakes

Ato

715

edits

@@ Line 47: / Line 47: @@
 ; ato
 : Then it sounds like we made the right technical decisions regarding architecture when we started out, and I’m happy you didn’t have to go back and change it.
-: However, precisely because it builds on top of what we already have, does it make sense for us to punt this until after we’ve landed the initial prototype in central?
+: However, ''precisely'' because it builds on top of what we already have, does it make sense for us to punt this until after we’ve landed the initial prototype in central?
 ; ochameau
-: HYour patch to the HTTP is more important, otherwise we won’t be compatible with anything.
+: Your patch to the HTTP is more important, otherwise we won’t be compatible with anything.
 : My work will make it possible for us to then connect to Puppeteer, but it won’t work without the HTTP fix.
 ; AutomatedTester
@@ Line 55: / Line 55: @@
 : I know you said “by end of last week” before, but we obviously missed that.
 ; ato
-: Yes, we were obviously derailed by some politics last week.
 : It largely depends on how quickly we can get a review from the build peers.
 : As ted suggested, the patch itself will ship with <code>r=ochameau,ato</code>.
@@ Line 62: / Line 61: @@
 : Then if I help out to get the build peers’ attention, we can land it by Wednesday?
 ; ato
-: I think that would be reasonable.
+: I think that would be a reasonable estimate.
 : I will have the HTTP fix in by end of today.
 : Alex, it would be good if you could start the secondary cursory review now.