Kate Middleton's flying dress coverage sparks Twitter outrage

Must have been a slow news day


Entertainment Desk April 12, 2016
Must have been a slow news day. PHOTO: VANITYFAIR

Being British Royalty may mean that Prince William and Kate Middleton are forever in the public eye, but that's no excuse for reporting the couple's every move and then publishing it in bad taste.

Times of India printed a photo -- on front page -- of the Duchess of Cambridge at the India Gate where she had gone to mark Queen Elizabeth's 90th birthday. The photo published however, was not of her placing a wreath at the tomb of a soldier, but was of a brief moment when... wait for it... a gust of wind happened to blow Kate's dress a little higher than expected.

Britain's William and Kate to visit Taj Mahal on India tour

Many have taken to Twitter to reprimand Times of India for its poor reporting.




https://twitter.com/GurleenRawal/status/719779926610735105

William makes dosa, royal couple meet top Indian fan



https://twitter.com/uday_bhan/status/719709814960562176

Although Times of India seems to be getting the brunt of it all, other notable publications have also published the story, including Vanity Fair and E! News. 



UK's Daily Mail takes the cake however, with the headline, "Kate's Marilyn moment: Duchess struggles to control her £1,700 dress as she and William lay a wreath at Delhi war memorial."



10 highlights from Prince William and Kate's Bollywood gala

This was the oh-so-brief moment that has made headlines all over the world:


Must have been a slow news day.

COMMENTS (11)

Chan | 7 years ago | Reply They are our guest. It's not fair to treat this way.
Allaisa Xuver | 7 years ago | Reply The Queen advised her to wear weighted skirts precisely to avoid such wardrobe malfunctions but Kate refuses to do it. This is not the first time nor will it be the last time.
VIEW MORE COMMENTS
Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ