US approves bill to appoint special envoy for combating Islamophobia

US House voted on proposal authored by Ilhan Omar to address anti-Muslim bias


Reuters December 16, 2021
US Congress representative Ilhan Omar. PHOTO: AFP/FILE

WASHINGTON:

The US House of Representatives voted on Tuesday to approve a Democratic proposal for a US State Department office to address anti-Muslim bias, after a Republican congresswoman used an Islamophobic slur against a Democratic colleague.

The House backed the bill in a party-line vote of 219-212.

The bill, authored by Representative Ilhan Omar, would create a special envoy for monitoring and combating Islamophobia and include state-sponsored anti-Muslim violence in the department's annual human rights reports.

"We are in the midst of a staggering rise of anti-Muslim violence and discrimination around the world," Omar said on the House floor. "Islamophobia is global in scope and we must lead the global effort to address it."

The House vote comes a few weeks after video emerged showing first-term Republican lawmaker Lauren Boebert calling Omar, a Muslim second-term congresswoman who was born in Somalia, a member of a "jihad squad".

Also read: Republican lawmaker apologises for calling Muslim MP ‘jihad squad’ member 

That comment led to calls by Democrats for a vote to strip Boebert of her committee assignments, as well as criticism by fellow Republican Representative Nancy Mace.

Republicans have decried the bill, calling it rushed and partisan.

Debate on the bill stalled for about an hour after Republican congressman Scott Perry accused Omar of being anti-Semitic and affiliated with terrorist organisations. The House chair ruled Perry's words on the House floor impugned Omar's reputation and were inappropriate.

Aides for Senate Democratic leader Chuck Schumer did not respond to requests for comment about the bill. Its fate in that chamber is unclear.

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