Description: Product Version: 5.3.0.3 Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1 Locale: en-US (en_US); As per Release notes https://wiki.documentfoundation.org/ReleaseNotes/5.3 there are new array ending including crows foot ending but they are missing in 5.3.0.3 Attached is a file for new array ending which are missing. Actual Results: Put 2 shapes and connect them using a connector. right click connector > go to line properties and try to change array heading. as per release notes crow foot array heading should be there but they are not available. Expected Results: As per release notes for 5.3.0 new arrow heading should be available. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:51.0) Gecko/20100101 Firefox/51.0
Created attachment 130900 [details] LO File with various arraow heads various arrow heads which are suppose to be in 5.3.0.3 but are missing.
You can refere to issues tdf#93782 tdf#92152
Spelling mistake (typo) Read array as arrow
(In reply to vkmr2012 from comment #0) > Description: > Product > Version: 5.3.0.3 > Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1 > Locale: en-US (en_US); > > As per Release notes https://wiki.documentfoundation.org/ReleaseNotes/5.3 > there are new arrow ending including crows foot ending but they are missing > in 5.3.0.3 > > Attached is a file for new arrow ending which are missing. > > > > Actual Results: > Put 2 shapes and connect them using a connector. right click connector > go > to line properties and try to change array heading. as per release notes > crow foot arrow heading should be there but they are not available. > > Expected Results: > As per release notes for 5.3.0 new arrow heading should be available. > > > Reproducible: Always > > User Profile Reset: No > > Additional Info: > > > User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:51.0) Gecko/20100101 Firefox/51.0
As per instruction given at URI https://wiki.documentfoundation.org/UserProfile I have reset the profile and issue is fixed. Please closed this bug as resolved. Sorry for the inconvenience. Good Luck.