Question: I am at a loss with why one page on a site that just went live is misbehaving on iPhone (and possibly others at 320 to 480 px wide.

I have used various simulators that have never let me down before (screenfly & iphone5 simulator) plus I have tested the responsiveness using browser resize and for some reason none of these methods can replicate the issue so I cannot find a way to correct the problem. I have cleared my cache and tried from a different phone. 

The Problem:

Visit (site removed) from a phone and notice that this is the only page on the website that does not fill the devices screen. Visit any other page and you will see that the rest all fill the page normally. 

If someone can point me in a direction to reproduce the problem (not on a phone) where I can access developer tools I should be able to correct the problem on my own. 

I have tried reviewing my code to see what is different about that page in comparison to every other page and cannot find what appears to be causing the problem. 

Some help would be gratefully appreciated.

Thank you in advance.

Answer: 
You need to be able to match across multiple lines. You are looking for the `s` (*dotall*) modifier. Unfortunately this modifier **does not** exist in JavaScript. A common workaround is replacing the dot `.` with the following:

```
[\S\s]    

```

So you can use the following regular expression:

```
/# userid name uniqueid connected ping loss state rate([\S\s]*?)#end/

```

**Explanation**:

```
(               # group and capture to \1:
  [\S\s]*?      #   any character of: 
                #    non-whitespace (all but \n, \r, \t, \f, and " "), 
                #    whitespace (\n, \r, \t, \f, and " ") 
                #    (0 or more times matching the least amount possible)
)               # end of \1

```

[JavaScript Demo](https://eval.in/171970)
You can use this pattern that uses the fact that "#end" is at the start of a line:

```
/# userid name uniqueid connected ping loss state rate\n((?:.*\n)*?)#end/

```

But an other efficient way is to split the log into lines and to look at the start and end lines in the resulting list.