Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a22eefdf79db2a83

Jump to content

Talk:Smoke screen

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 3 years ago by Info-Deathmatch in topic References? Sources? Citations?

origins and other smokes

[edit]

Modern military smoke projectiles may have started with British WP shells in WW1, similarly the base ejection HC smoke shell seems to have invented by the British in the 1930s. However, in WW2 German smoke shells seem to have used oleum. In 1950s UK designed marker shells to produce an instantaneous cloud of coloured smoke, these used PETN and dye. Red phosphorus smoke grenades seem to have been used in WW2.

Clearly this entry needs more work. Nfe (talk) 03:47, 18 January 2008 (UTC)Reply

Smoke as a RADAR Obstruction

[edit]

How thick does smoke have to be to block and interfere with RADAR Waves? --Arima (talk) 23:22, 19 June 2009 (UTC)Reply

References? Sources? Citations?

[edit]

Hi, this interesting article has quite a lot of information without quoting verifiable references. Can please the contibutors provide those used when editing the article? I'll tag it to facilitate resolution of this issue.
Thanks & regards, DPdH (talk) 13:34, 14 August 2009 (UTC)Reply


References? Sources? Citations?

[edit]

Reference number 5 seems to be very suspect, at best.  Preceding unsigned comment added by 40.142.211.170 (talk) 21:47, 23 June 2022 (UTC)Reply

Seems like smoke-related military articles could use more work overall... Info-Deathmatch (talk) 14:28, 30 September 2022 (UTC)Reply