2 clarified "button" confusion
source | link

What's wrong with:

FirstPrev [First] [Prev] ... 456[4] [5] ... NextLast[6] [Next] [Last]

It has been commonly used in little-space-for-paging situations.

As per:

I may only edit the CSS of the original (desktop) interface to adapt it to a mobile environment. I may not add or remove any of the already present elements

You can remove elements with css (display:none) and use media queries to do so depending on viewport size.

What's wrong with:

FirstPrev ... 456 ... NextLast

It has been commonly used in little-space-for-paging situations.

As per:

I may only edit the CSS of the original (desktop) interface to adapt it to a mobile environment. I may not add or remove any of the already present elements

You can remove elements with css (display:none) and use media queries to do so depending on viewport size.

What's wrong with:

[First] [Prev] ... [4] [5] ... [6] [Next] [Last]

It has been commonly used in little-space-for-paging situations.

As per:

I may only edit the CSS of the original (desktop) interface to adapt it to a mobile environment. I may not add or remove any of the already present elements

You can remove elements with css (display:none) and use media queries to do so depending on viewport size.

1
source | link

What's wrong with:

FirstPrev ... 456 ... NextLast

It has been commonly used in little-space-for-paging situations.

As per:

I may only edit the CSS of the original (desktop) interface to adapt it to a mobile environment. I may not add or remove any of the already present elements

You can remove elements with css (display:none) and use media queries to do so depending on viewport size.