Won't Display More Than 999 Rows in Chrome
up vote
0
down vote
favorite
For some reason, in Chrome, elements begin overlapping one another once 999 rows have been printed. It works fine in Firefox. The version of Chrome that I'm using is 70.0.3538.102 (Official Build) (64-bit), which was just released earlier today.
The pages are sorted alphabetically, and I don't experience this issue on any other page because the 'A' page is the only page with more than 999 rows.
#data {
display: grid;
grid-template-columns: repeat(8, max-content);
grid-template-rows: auto;
}
<section id="data">
...
<div>1000</div><div>axelle</div><div>G</div><div>92,296</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1001</div><div>axes</div><div>G</div><div>88,536</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1002</div><div>axethrowing</div><div>G</div><div>138,823</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1003</div><div>axial</div><div>G</div><div>395,943</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1004</div><div>axialracing</div><div>G</div><div>165,508</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1005</div><div>axilas</div><div>G</div><div>87,736</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1006</div><div>axiom</div><div>G</div><div>110,834</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1007</div><div>axioo</div><div>G</div><div>321,874</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div>
...
</section>
Is this a Chrome bug or?
html css
google-chrome css-grid asked Nov 10 at 4:44
Anthony
1,259325
add a comment |
up vote
0
down vote
favorite
For some reason, in Chrome, elements begin overlapping one another once 999 rows have been printed. It works fine in Firefox. The version of Chrome that I'm using is 70.0.3538.102 (Official Build) (64-bit), which was just released earlier today.
The pages are sorted alphabetically, and I don't experience this issue on any other page because the 'A' page is the only page with more than 999 rows.
#data {
display: grid;
grid-template-columns: repeat(8, max-content);
grid-template-rows: auto;
}
<section id="data">
...
<div>1000</div><div>axelle</div><div>G</div><div>92,296</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1001</div><div>axes</div><div>G</div><div>88,536</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1002</div><div>axethrowing</div><div>G</div><div>138,823</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1003</div><div>axial</div><div>G</div><div>395,943</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1004</div><div>axialracing</div><div>G</div><div>165,508</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1005</div><div>axilas</div><div>G</div><div>87,736</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1006</div><div>axiom</div><div>G</div><div>110,834</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1007</div><div>axioo</div><div>G</div><div>321,874</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div>
...
</section>
Is this a Chrome bug or?
html css
google-chrome css-grid asked Nov 10 at 4:44
Anthony
1,259325
Please show us the markup and CSS that you're using. (Are you actually using CSS Grid, not an HTML table?)
– duskwuff
Nov 10 at 5:02
@duskwuff added, although i don't think it's an issue with the HTML/CSS since it works fine in firefox
– Anthony
Nov 10 at 5:09
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
For some reason, in Chrome, elements begin overlapping one another once 999 rows have been printed. It works fine in Firefox. The version of Chrome that I'm using is 70.0.3538.102 (Official Build) (64-bit), which was just released earlier today.
The pages are sorted alphabetically, and I don't experience this issue on any other page because the 'A' page is the only page with more than 999 rows.
#data {
display: grid;
grid-template-columns: repeat(8, max-content);
grid-template-rows: auto;
}
<section id="data">
...
<div>1000</div><div>axelle</div><div>G</div><div>92,296</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1001</div><div>axes</div><div>G</div><div>88,536</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1002</div><div>axethrowing</div><div>G</div><div>138,823</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1003</div><div>axial</div><div>G</div><div>395,943</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1004</div><div>axialracing</div><div>G</div><div>165,508</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1005</div><div>axilas</div><div>G</div><div>87,736</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1006</div><div>axiom</div><div>G</div><div>110,834</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1007</div><div>axioo</div><div>G</div><div>321,874</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div>
...
</section>
Is this a Chrome bug or?
html css
google-chrome css-grid asked Nov 10 at 4:44
Anthony
1,259325
For some reason, in Chrome, elements begin overlapping one another once 999 rows have been printed. It works fine in Firefox. The version of Chrome that I'm using is 70.0.3538.102 (Official Build) (64-bit), which was just released earlier today.
The pages are sorted alphabetically, and I don't experience this issue on any other page because the 'A' page is the only page with more than 999 rows.
#data {
display: grid;
grid-template-columns: repeat(8, max-content);
grid-template-rows: auto;
}
<section id="data">
...
<div>1000</div><div>axelle</div><div>G</div><div>92,296</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1001</div><div>axes</div><div>G</div><div>88,536</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1002</div><div>axethrowing</div><div>G</div><div>138,823</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1003</div><div>axial</div><div>G</div><div>395,943</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1004</div><div>axialracing</div><div>G</div><div>165,508</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1005</div><div>axilas</div><div>G</div><div>87,736</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1006</div><div>axiom</div><div>G</div><div>110,834</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div><div>1007</div><div>axioo</div><div>G</div><div>321,874</div><div>2018-11-09</div><div>NULL</div><div>0</div><div>2018-11-09 07:49:36</div>
...
</section>
Is this a Chrome bug or?
html css
google-chrome css-grid html css
google-chrome css-grid asked Nov 10 at 4:44
Anthony
1,259325
asked Nov 10 at 4:44
Anthony
1,259325
edited Nov 10 at 5:09
asked Nov 10 at 4:44
Anthony
1,259325
asked Nov 10 at 4:44
Anthony
1,259325
asked Nov 10 at 4:44
Anthony
1,259325
1,259325
Please show us the markup and CSS that you're using. (Are you actually using CSS Grid, not an HTML table?)
– duskwuff
Nov 10 at 5:02
@duskwuff added, although i don't think it's an issue with the HTML/CSS since it works fine in firefox
– Anthony
Nov 10 at 5:09
add a comment |
Please show us the markup and CSS that you're using. (Are you actually using CSS Grid, not an HTML table?)
– duskwuff
Nov 10 at 5:02
@duskwuff added, although i don't think it's an issue with the HTML/CSS since it works fine in firefox
– Anthony
Nov 10 at 5:09
Please show us the markup and CSS that you're using. (Are you actually using CSS Grid, not an HTML table?)
– duskwuff
Nov 10 at 5:02
Please show us the markup and CSS that you're using. (Are you actually using CSS Grid, not an HTML table?)
– duskwuff
Nov 10 at 5:02
@duskwuff added, although i don't think it's an issue with the HTML/CSS since it works fine in firefox
– Anthony
Nov 10 at 5:09
@duskwuff added, although i don't think it's an issue with the HTML/CSS since it works fine in firefox
– Anthony
Nov 10 at 5:09
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
The CSS Grid specification makes explicit provisions for the handling of very large grids:
Since memory is limited, UAs may clamp the possible size of the grid to be within a UA-defined limit, dropping all lines outside that limit. If a grid item is placed outside this limit, its grid area must be clamped to within this limited grid.
(https://www.w3.org/TR/css-grid-1/#overlarge-grids)
The specification goes on to give an example involving a hypothetical UA with a grid size limit of 1000, implying that this is a typical limit.
This is not an appropriate application for CSS Grid functionality. Use an HTML table -- this is exactly the sort of thing they're made for.
answered Nov 10 at 5:14
duskwuff
145k19176229
ok thanks. not sure why Chrome would implement the limit, whereas it's all good in Firefox :/ what is UA?
– Anthony
Nov 10 at 5:17
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236054%2fwont-display-more-than-999-rows-in-chrome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
The CSS Grid specification makes explicit provisions for the handling of very large grids:
Since memory is limited, UAs may clamp the possible size of the grid to be within a UA-defined limit, dropping all lines outside that limit. If a grid item is placed outside this limit, its grid area must be clamped to within this limited grid.
(https://www.w3.org/TR/css-grid-1/#overlarge-grids)
The specification goes on to give an example involving a hypothetical UA with a grid size limit of 1000, implying that this is a typical limit.
This is not an appropriate application for CSS Grid functionality. Use an HTML table -- this is exactly the sort of thing they're made for.
answered Nov 10 at 5:14
duskwuff
145k19176229
ok thanks. not sure why Chrome would implement the limit, whereas it's all good in Firefox :/ what is UA?
– Anthony
Nov 10 at 5:17
add a comment |
up vote
0
down vote
accepted
The CSS Grid specification makes explicit provisions for the handling of very large grids:
Since memory is limited, UAs may clamp the possible size of the grid to be within a UA-defined limit, dropping all lines outside that limit. If a grid item is placed outside this limit, its grid area must be clamped to within this limited grid.
(https://www.w3.org/TR/css-grid-1/#overlarge-grids)
The specification goes on to give an example involving a hypothetical UA with a grid size limit of 1000, implying that this is a typical limit.
This is not an appropriate application for CSS Grid functionality. Use an HTML table -- this is exactly the sort of thing they're made for.
answered Nov 10 at 5:14
duskwuff
145k19176229
ok thanks. not sure why Chrome would implement the limit, whereas it's all good in Firefox :/ what is UA?
– Anthony
Nov 10 at 5:17
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
The CSS Grid specification makes explicit provisions for the handling of very large grids:
Since memory is limited, UAs may clamp the possible size of the grid to be within a UA-defined limit, dropping all lines outside that limit. If a grid item is placed outside this limit, its grid area must be clamped to within this limited grid.
(https://www.w3.org/TR/css-grid-1/#overlarge-grids)
The specification goes on to give an example involving a hypothetical UA with a grid size limit of 1000, implying that this is a typical limit.
This is not an appropriate application for CSS Grid functionality. Use an HTML table -- this is exactly the sort of thing they're made for.
answered Nov 10 at 5:14
duskwuff
145k19176229
The CSS Grid specification makes explicit provisions for the handling of very large grids:
Since memory is limited, UAs may clamp the possible size of the grid to be within a UA-defined limit, dropping all lines outside that limit. If a grid item is placed outside this limit, its grid area must be clamped to within this limited grid.
(https://www.w3.org/TR/css-grid-1/#overlarge-grids)
The specification goes on to give an example involving a hypothetical UA with a grid size limit of 1000, implying that this is a typical limit.
This is not an appropriate application for CSS Grid functionality. Use an HTML table -- this is exactly the sort of thing they're made for.
answered Nov 10 at 5:14
duskwuff
145k19176229
answered Nov 10 at 5:14
duskwuff
145k19176229
answered Nov 10 at 5:14
duskwuff
145k19176229
answered Nov 10 at 5:14
duskwuff
145k19176229
145k19176229
ok thanks. not sure why Chrome would implement the limit, whereas it's all good in Firefox :/ what is UA?
– Anthony
Nov 10 at 5:17
add a comment |
ok thanks. not sure why Chrome would implement the limit, whereas it's all good in Firefox :/ what is UA?
– Anthony
Nov 10 at 5:17
ok thanks. not sure why Chrome would implement the limit, whereas it's all good in Firefox :/ what is UA?
– Anthony
Nov 10 at 5:17
ok thanks. not sure why Chrome would implement the limit, whereas it's all good in Firefox :/ what is UA?
– Anthony
Nov 10 at 5:17
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236054%2fwont-display-more-than-999-rows-in-chrome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please show us the markup and CSS that you're using. (Are you actually using CSS Grid, not an HTML table?)
– duskwuff
Nov 10 at 5:02
@duskwuff added, although i don't think it's an issue with the HTML/CSS since it works fine in firefox
– Anthony
Nov 10 at 5:09