Safari specific issues

[filfreire]

Issues found with elements not being inline and position of the elements for Safari

[filfreire]

After some investigation, it seems the page-break-* rules don't work properly for Safari, in this case affecting the display of labels and inputs.

Unfortunately page-break-after works differently from browser to browser, one cannot assume a behavior and we thus need to revert to a simpler, known behavior.
(source: https://stackoverflow.com/a/37604027)

There are a few bugs reported related to Webkit and page-break-* rules, example: https://bugs.webkit.org/show_bug.cgi?id=5097

Another way of creating the break after these elements were attempted, following answer https://stackoverflow.com/a/10934138 and it worked for all elements, except input and label elements, the ones affected by the issue.

For input elements, in particular, this workaround reportedly also doesn't work because of the input elements specification, as shown in https://stackoverflow.com/a/4574946 and https://stackoverflow.com/a/27708091

@yegor256 I think we should close this issue, WDYT?

[yegor256]

@filfreire well, the page looks wrong in Safari. We have to find some solution. Can we?

[0crat]

Job #79 is now in scope, role is DEV

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

Bug was reported, see §29: +15 point(s) just awarded to @filfreire/z

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@filfreire/z everybody who has role DEV is banned at #79; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)