Fabrice
VIP Members
- Joined
- Mar 30, 2017
- Messages
- 2,138
- Reaction score
- 454
- Location
- The Netherlands
- My Car
-
73 Grande 351C
71 Mach 1 429CJ
@7173Mustang @RocketFoot
Hey guys,
ok, so I've just posted an update to my thread and took some screenshots of some problems
Only Chrome works on mac.
Safari and FF both fail to upload files.
Smell like someone expect the tmp blob address returned on http request Status after upload, and bets on the wrong request status code.
That's basic request js coding and should be easy fix.
Next, is the IMG insert.
I do miss the intuitive drag drop region. Dunno why they replaced it with this old fashion 2 extra steps way.
Anyway once it's finally in there, the long awaited insert at full width is there to make you forget that detail!! Woohoo!
Unfortunately, the old bug is still ruining the party
here to illustrate:
if I upload an image where the natural width is greater than its natural height: no problem. The image is then displayed 100% of its parent container.
but
Now an image where the natural height is greater than the natural width, the insert fails. It fails exponentially based on the image height. Because the basic math that is supposed to calculate the in ratio reduction percentage is wrong.
Both images should have the inline width set to the exact same value, in this template case: 956. Not 810 as the container parent is the same.
When I say "should have the inline width", I mean that because they are ment to be displayed in the same container, they should have the same value, but in fact there should not even be there! A basic container.img css with 100% would do it automatically! The insert full option should not even generate the inline strings, only when a size smaller than the natural width within that container should. At least even if this html is wrong, by fixing this basic resizing method to generate the correct inline width and height strings, the display of the images would be as expected.
@7173Mustang @RocketFoot
I know you guys are depending on the soft as is, if you have the php template/js that spit the page string available, I'd gladly help.
@7173Mustang
News regarding the fix of the previous uploads now displayed in low res thumbnails?
Hey guys,
ok, so I've just posted an update to my thread and took some screenshots of some problems
Only Chrome works on mac.
Safari and FF both fail to upload files.

Smell like someone expect the tmp blob address returned on http request Status after upload, and bets on the wrong request status code.
That's basic request js coding and should be easy fix.
Next, is the IMG insert.
I do miss the intuitive drag drop region. Dunno why they replaced it with this old fashion 2 extra steps way.
Anyway once it's finally in there, the long awaited insert at full width is there to make you forget that detail!! Woohoo!
Unfortunately, the old bug is still ruining the party
here to illustrate:

if I upload an image where the natural width is greater than its natural height: no problem. The image is then displayed 100% of its parent container.
but

Now an image where the natural height is greater than the natural width, the insert fails. It fails exponentially based on the image height. Because the basic math that is supposed to calculate the in ratio reduction percentage is wrong.
Both images should have the inline width set to the exact same value, in this template case: 956. Not 810 as the container parent is the same.
When I say "should have the inline width", I mean that because they are ment to be displayed in the same container, they should have the same value, but in fact there should not even be there! A basic container.img css with 100% would do it automatically! The insert full option should not even generate the inline strings, only when a size smaller than the natural width within that container should. At least even if this html is wrong, by fixing this basic resizing method to generate the correct inline width and height strings, the display of the images would be as expected.
@7173Mustang @RocketFoot
I know you guys are depending on the soft as is, if you have the php template/js that spit the page string available, I'd gladly help.
@7173Mustang
News regarding the fix of the previous uploads now displayed in low res thumbnails?