You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A line break is inserted into the rendered list of flags when the 18th flag is found. If a line of flags has exactly 18 flags then an unnecessary and unattractive br produces excess line spacing. See source
I noticed this issue while looking for stray newlines in the roster produced while scraping the federation.
A better algorithm would terminate the first line when the 19th flag was encountered. Even more complex logic could then omit the br should the line be found to stand at 18 when advancing to a new section.
This code has other problems in some versions of ie where 18 is one too many flags for a line. I note this spacing problem here in case anyone ever tackles the other count based line breaking limitations of this plugin.
The text was updated successfully, but these errors were encountered:
We're much more likely to see this problem with the Visible Federation scrape result where the white space has strong semantics. See WardCunningham/search#8
A line break is inserted into the rendered list of flags when the 18th flag is found. If a line of flags has exactly 18 flags then an unnecessary and unattractive br produces excess line spacing. See source
I noticed this issue while looking for stray newlines in the roster produced while scraping the federation.
A better algorithm would terminate the first line when the 19th flag was encountered. Even more complex logic could then omit the br should the line be found to stand at 18 when advancing to a new section.
This code has other problems in some versions of ie where 18 is one too many flags for a line. I note this spacing problem here in case anyone ever tackles the other count based line breaking limitations of this plugin.
The text was updated successfully, but these errors were encountered: