2017 Aegon International Eastbourne – Women's Doubles
Darija Jurak and Anastasia Rodionova were the defending champions, but lost in the first round to Ekaterina Makarova and Elena Vesnina.
Women's Doubles | |
---|---|
2017 Aegon International Eastbourne | |
Champions | |
Runners-up | |
Final score | 6–3, 7–5 |
Chan Yung-jan and Martina Hingis won the title, defeating Ashleigh Barty and Casey Dellacqua in the final, 6–3, 7–5.
Seeds
Ekaterina Makarova / Elena Vesnina (Quarterfinals, withdrew) Chan Yung-jan / Martina Hingis (Champions) Tímea Babos / Andrea Hlaváčková (Semifinals) Lucie Hradecká / Kateřina Siniaková (First round)
Draw
Key
- Q = Qualifier
- WC = Wild Card
- LL = Lucky Loser
- Alt = Alternate
- SE = Special Exempt
- PR = Protected Ranking
- ITF = ITF entry
- JE = Junior Exempt
- w/o = Walkover
- r = Retired
- d = Defaulted
Draw
First Round | Quarterfinals | Semifinals | Final | ||||||||||||||||||||||||
1 | 6 | 6 | |||||||||||||||||||||||||
1 | 0 | 1 | |||||||||||||||||||||||||
6 | 6 | | w/o | ||||||||||||||||||||||||
2 | 3 | 6 | 6 | ||||||||||||||||||||||||
3 | 6 | 4 | [10] | 3 | 2 | 3 | |||||||||||||||||||||
3 | 6 | [6] | 3 | 2 | 6 | [10] | |||||||||||||||||||||
w/o | 6 | 0 | [5] | ||||||||||||||||||||||||
3 | 5 | ||||||||||||||||||||||||||
4 | 7 | [7] | 2 | 6 | 7 | ||||||||||||||||||||||
6 | 5 | [10] | 2r | ||||||||||||||||||||||||
WC | 77 | 6 | WC | 3 | |||||||||||||||||||||||
4 | 65 | 2 | WC | 0 | 1 | ||||||||||||||||||||||
64 | 1 | 2 | 6 | 6 | |||||||||||||||||||||||
77 | 6 | 2 | 0 | ||||||||||||||||||||||||
1 | 2 | 2 | 6 | 6 | |||||||||||||||||||||||
2 | 6 | 6 |
gollark: API coherency: drop stuff like XMLHttpRequest which is obsoleted by cleaner things like `fetch`, actually have a module system and don't just randomly scatter objects and functions in the global scope, don't have a weird mix of callbacks, events and promises everywhere.
gollark: Alternatively, cross-origin stuff is allowed but runs with separate cookies, caches, etc. to first-party requests, and comes with a "requested from this origin" header.
gollark: Cross-origin fixes: *no* use of crossdomain resources unless the other thing opts in. This breaks image hotlinking and such, which is annoying, but fixes CSRF entirely.
gollark: That doesn't really help with the security issues though.
gollark: Maybe a standard interface for external plugins for access to that stuff, so browsers wouldn't need to implement all the APIs individually?
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.